I was messing around flashing roms(last flash was oneplus aosp) with twrp and I lost my modem(baseband) and do not have voice or data. I tried flashing just NON-HLOS.bin but did not regain the baseband. I also fastboot flashed all the files to stock ROM and still have missing baseband. Right now it is rebooting everytime I restart. What to do?
check ur imei,is it available?
Sent from my One using XDA Premium 4 mobile app
RISHI RAJ said:
check ur imei,is it available?
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no. Oh no.....that's bad isn't it. Damn thing doesn't want to power off and reboots every few minutes.
Then you must have lost your efs folder.Guess its the same like in samsung phones.There's a fix in samsung note 3 thread about fixing corrupted efs partition but not sure it will work or not
Sent from my One using XDA Premium 4 mobile app
Great, out of all phones I've ever had this one gives me a problem......
Sent from my ME302C using Tapatalk
RISHI RAJ said:
Then you must have lost your efs folder.Guess its the same like in samsung phones.There's a fix in samsung note 3 thread about fixing corrupted efs partition but not sure it will work or not
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I ask you if you have and /efs folder in the root of the device?
tdamocles said:
Can I ask you if you have and /efs folder in the root of the device?
Click to expand...
Click to collapse
Even if we did, we wouldn't be able to provide you with a backup as it contains the IMEI for an individual's phone. The best we can do, is try to salvage the data inside your /efs partition. If it's been fully wiped (as in deleted), then recovering the data might be possible, but you'll have to make a bit-by-bit shadow copy of the /efs partition. I think it's ext4, but I'm not sure. It is possible to recover the data, if it's simply been deleted. If it's been overwritten, then I'm afraid you'll be out of luck.
No one can provide his or her imei.You must visit note 3 forum sd variant.They will guide you to the thread which has a zip to fix it(if only it can work for your phone)
Sent from my One using XDA Premium 4 mobile app
Desolutional said:
Even if we did, we wouldn't be able to provide you with a backup as it contains the IMEI for an individual's phone. The best we can do, is try to salvage the data inside your /efs partition. If it's been fully wiped (as in deleted), then recovering the data might be possible, but you'll have to make a bit-by-bit shadow copy of the /efs partition. I think it's ext4, but I'm not sure. It is possible to recover the data, if it's simply been deleted. If it's been overwritten, then I'm afraid you'll be out of luck.
Click to expand...
Click to collapse
Yes I understand but I don't see the partition anyway looking for it between the reboots that I am having.
try flashing color os in fastboot,maybe that can help
Sent from my SM-N900 using XDA Premium 4 mobile app
tdamocles said:
Can I ask you if you have and /efs folder in the root of the device?
Click to expand...
Click to collapse
Just checked. There is no efs folder in the root directory. For what's it's worth the imei number is printed on a sticker on top of your OPO box. Not that it's much help right now.
newellj79 said:
Just checked. There is no efs folder in the root directory. For what's it's worth the imei number is printed on a sticker on top of your OPO box. Not that it's much help right now.
Click to expand...
Click to collapse
Waiting for my oppo(processing shipping) - anyway, about this open a ticket support to opo, you might have to send the phone back
Not the best way and you'll pay something as this a software issue that was caused from you but it's better than having a multimedia player
EDIT: Chanced to Pending Shipment ..heh nice (I'm acting like a kid lol)
Did you make any kind of backup of your previous rom? I had the same issue at one point with my n5 and my samsung note 2. You can also try flashing the stock image which I think they have on the oneplusone forum or something and that may bring up the efs that is hidden somewhere. Let me know.
yankees45us said:
Did you make any kind of backup of your previous rom? I had the same issue at one point with my n5 and my samsung note 2. You can also try flashing the stock image which I think they have on the oneplusone forum or something and that may bring up the efs that is hidden somewhere. Let me know.
Click to expand...
Click to collapse
I did have 2 nandroids of 2 different roms but I restored them both and it did not help. Then I flashed by fastboot all of the files of cm11s and lost the nandroids. I forget to offload the nandroids externally.
tdamocles said:
I did have 2 nandroids of 2 different roms but I restored them both and it did not help. Then I flashed by fastboot all of the files of cm11s and lost the nandroids. I forget to offload the nandroids externally.
Click to expand...
Click to collapse
So you have no backups now and you have tried flashing the stock cm11s software?
Sent from my One using XDA Free mobile app
yankees45us said:
So you have no backups now and you have tried flashing the stock cm11s software?
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
yes.
tdamocles said:
yes.
Click to expand...
Click to collapse
I had a similar issue but I was able to flash the old data from an old backup and somehow get my efs back. Has oneplus gotten back to you? This should be covered under the warranty.
Sent from my One using XDA Free mobile app
yankees45us said:
I had a similar issue but I was able to flash the old data from an old backup and somehow get my efs back. Has oneplus gotten back to you? This should be covered under the warranty.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
submitted Sunday and no response.....
Count me in, same goes with me, also no baseband anymore, opened call on sunday and just got this as answer :
OnePlus QC said:
We don't support Custom Recovery like CWM. Here are the instructions to re-flash CM Recovery:
You'll need Android ADB drivers installed first, for which you can use the standard Google Android SDK drivers if you're using Windows: https://developer.android.com/sdk/win-usb.html
Afterwards, follow these steps:
0) Backup everything important you have on the device. Flashing will erase all data from your phone.
1) Download http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed-fastboot.zip
and unzip to you /android-sdk/platform-tools folder (for easy access)
2) Turn off device, then press the power and hold the Volume Up button until the device shows the fastboot screen
3) Start the fastboot tool and run the following in the command line (that means, windows+r, type cmd, press enter), in sequence:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
4) Still using the same command line, enter "fastboot reboot" to reboot your OnePlus One into CyanogenMod
Hope this helps.
Click to expand...
Click to collapse
After which they overeagerly closed the service request
I've reopened it, though, as the case is far from solved.
Will redo this again tonight, so I do collaborate as they require, but it won't change anything as I've gone through this already
JP.
I don't know if it lets you but I would open a new case every 2 days till it gets resolved. This customer service issue is what is probably going to get me to sell my oneplus. I can't stand it. First its the yellow band which they should have replaced no questions asked and now this. And that's why companies like samsung, lg and others stay in business. I hope you get things figured out. Sorry about all that. Hopefully you have a backup phone in the meantime.
Related
Hi
where can I get the stock Firmware (and recovery) for the One Mini (international Edition)?
I've a crack on the Frame, near the volume buttons...and before i bring it back i need it to turn it stock...
thanks for any help
Have you tried to use the search function first? you would have found other threads discussing this, like this one: http://forum.xda-developers.com/showthread.php?t=2464227
Sent from my HTC One mini using xda app-developers app
http://androidruu.com/?developer=M4
You can get the ATT RUU from there in about 10mins.....
jmz said:
http://androidruu.com/?developer=M4
You can get the ATT RUU from there in about 10mins.....
Click to expand...
Click to collapse
I've searched everywhere, but can't find a UK/WWE stock image.... I need an untouched/unrooted 1.22.401.1
Surely somebody somewhere must have it?
It's driving me nuts.....
Thanks!
nelvinchi said:
I've searched everywhere, but can't find a UK/WWE stock image.... I need an untouched/unrooted 1.22.401.1
Surely somebody somewhere must have it?
It's driving me nuts.....
Thanks!
Click to expand...
Click to collapse
Nah I haven't seen it
nelvinchi said:
I've searched everywhere, but can't find a UK/WWE stock image.... I need an untouched/unrooted 1.22.401.1
Surely somebody somewhere must have it?
It's driving me nuts.....
Thanks!
Click to expand...
Click to collapse
here's a TWRP backup (1.22.401.1)
download
epolus said:
here's a TWRP backup (1.22.401.1)
download
Click to expand...
Click to collapse
that should be stickied till there's an RUU
Would this work across other one mini? With having different imei? Cheers.
Sent from my HTC One mini using xda app-developers app
RUU
Here is the ruu http://www.htc.com/us/support/news.aspx?p_id=655&p_name=htc-one-mini-att you need to be s-off. Just use the revone method. It's really easy. remove the tampered flag and change to locked instead of relock. I've done it on mines and it didn't brick my devices. I used the terminal emulator. GOOD LUCK !!!!! On your bootloader it will show locked and s-off if you done it correctly. I'm going to get a replacement today and hope that at&t won't check the s-off otherwise I'll be sad.
epolus said:
here's a TWRP backup (1.22.401.1)
download
Click to expand...
Click to collapse
ive tried to restore this backup but instead of being a clean 1.22 its showing up as 1.32 and giving me a warning about my phone being a test device so i cant turn off htc stats, anyone else found this ??
---------- Post added at 05:42 PM ---------- Previous post was at 05:18 PM ----------
RuffBuster said:
Would this work across other one mini? With having different imei? Cheers.
Sent from my HTC One mini using xda app-developers app
Click to expand...
Click to collapse
Backups just back up your system and apps etc it doesn't touch your imei
Sent from my HTC One mini using XDA Premium 4 mobile app
CONdemmedNORmal said:
ive tried to restore this backup but instead of being a clean 1.22 its showing up as 1.32 and giving me a warning about my phone being a test device so i cant turn off htc stats, anyone else found this ??
Click to expand...
Click to collapse
on what Version was your mini before?
on my device it worked...(and it's not the device from the backup)
here are the steps i did...
copy the backup inside the twrp Folder
flashed the boot.emmc.win via fastboot (is inside the zip)
Code:
fastboot erase cacheCode:
fastboot flash boot boot.emmc.winCode:
fastboot erase cacheFull Wipe im Recovery ausführen
(wipe Data/Cache/Dalvik/System not the SD)
restored backup via twrp
Code:
fastboot erase cacheCode:
fastboot flash the stock recovery.img
fastboot erase cache
locked the bootloader via fastboot
Code:
fastboot oem lock
reboot...finish...
epolus said:
on what Version was your mini before?
on my device it worked...(and it's not the device from the backup)
here are the steps i did...
copy the backup inside the twrp Folder
flashed the boot.emmc.win via fastboot (is inside the zip)
Code:
fastboot erase cacheCode:
fastboot flash boot boot.emmc.winCode:
fastboot erase cacheFull Wipe im Recovery ausführen
(wipe Data/Cache/Dalvik/System not the SD)
restored backup via twrp
Code:
fastboot erase cacheCode:
fastboot flash the stock recovery.img
fastboot erase cache
locked the bootloader via fastboot
Code:
fastboot oem lock
reboot...finish...
Click to expand...
Click to collapse
I'm not really sure I got the device, make a back up but flashing a new Rom deleted it, used to Sony where doing something doesn't also wipe your internal memory, and have had quite abit of trouble trying to get back to complete stock, quite annoying really "/
Sent from my HTC One mini using XDA Premium 4 mobile app
Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!
While flashing the stock images make sure you have also Erased cache partition and formatted it using stock recovery.. I was exactly in the same spot as you were few weeks ago and a cache partition format solved it completely!
Koopa777 said:
Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!
Click to expand...
Click to collapse
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.
prabs99 said:
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.
Click to expand...
Click to collapse
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk
Koopa777 said:
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5
Pirateghost said:
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5
Click to expand...
Click to collapse
I've come to the conclusion, after 4(!) factory images, that the ROM DEFINITELY corrupts the recovery. I have a 100% success(failure?) rate when flashing PA. Clean md5, after first boot the ROM functions properly, but recovery fails to mount the userdata partition, every time. Flash a new recovery, or adb shell and attempt to repair don't work. I understand that it doesn't make sense, but it's obviously something that's happening with the ROM. After 4 factory images, the only other factors are the recovery(PhilZ, TWRP, AND CWM all fail) being borked from the start, or the ROM. It's obviously not the recovery(all 3 have clean md5s, are transferred with adb push, and function perfectly otherwise).....
Again, in the ROM I can r/w to the /data, so the partition is fine, but the ROM borks the recovery.
But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5
Pirateghost said:
But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5
Click to expand...
Click to collapse
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk
Koopa777 said:
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5
Pirateghost said:
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5
Click to expand...
Click to collapse
No. I can flash different ROMs, kernels, etc. Just not PA. The only thing of note was that my stock backup bootlooped when restoring with TWRP, but other than that no.
Sent from my Nexus 5 using Tapatalk
Nevermind, I just flashed liquidsmooth+Elementalx with PhilZ and it happened again. So what exactly is going on?
Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5
Pirateghost said:
Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope. Adb shell in Philz says repair failed. I found this
http://forum.xda-developers.com/google-nexus-5/help/unable-to-mount-data-issue-t2723993
http://forum.xda-developers.com/google-nexus-5/help/recovery-mount-data-t2639945
But neither helps. Recovery still can not mount /data.
I would RMA it.
Sent from my Nexus 5
I would try LG Flashtool it worked for me.
maxal said:
I would try LG Flashtool it worked for me.
Click to expand...
Click to collapse
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?
Koopa777 said:
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?
Click to expand...
Click to collapse
Yup, here is the link http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
I just called Google. RMA is inbound. It just kind of sucks, this phone was solid. No light bleed, no dead pixels, etc. Except for a loose power button.
Anyway I think it is definately a hardware issue, as my phone has been getting crazy hot lately. I know it's supposed to get hot, but this phone was scorching...Might have fried something.
I made a data dump backup of all important partitions needed to rescue your phone except for the bootloader.....these are phone specific due to a bootloader unlock key. You can locate all of these images using the link below.
I also created an ODIN flash-able rescue .tar in case you find yourself in a boot loop or other bricked state. This ODIN file contains a Stock rooted system image, stock boot image, and TWRP custom recovery. The name of this file is "GS5-DEV_VZWSTOCK_Rooted.tar.md5.7z" and it can be found by clicking the link below.
##CREDIT##
TWRP For their awesome recovery
Files include:
Main OS
system.img
recovery.img
boot.img
Radios
Modem.bin
ODIN Rescue FIle
GS5-DEV_VZWSTOCK_Rooted.tar.md5.7z
+Unpack ODIN File using 7zip
+Flash using ODIN 3.07 in PDA section
****DO NOT USE "JODIN" TO FLASH
+This will recover your phone back to a bootable state
+After flashing this via ODIN jump into TWRP recovery and wipe cache
+Reboot and you should be back to normal
+If you continue to have issues or force closing jump into TWRP and factory reset
Download Here
If you found this rescue image useful and want to buy me a beer the link is below...
Thanks to those who have donated already.
Donate here
Need testers for the ODIN flashable rescue file. Let me know if this works to rescue you from a brick state or loop
###FOR DEV VERSION ONLY###
EFS is device specific (IMEI, Mac-address and stuff). You should take it down.
Edit:- same with modemst1 and modemst2 (Snapdragon variants store their IMEI in those two partitions).
Walter.White said:
EFS is device specific (IMEI, Mac-address and stuff). You should take it down.
Edit:- same with modemst1 and modemst2 (Snapdragon variants store their IMEI in those two partitions).
Click to expand...
Click to collapse
Removed. POLLOS HERMONOS FO LIFE!!!
Sent from my SM-G900V using XDA Premium 4 mobile app
das7982 said:
Removed. POLLOS HERMONOS FO LIFE!!!
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
haha. One of the greatest show of all time.
By the way, you should left the modem.bin (block mmcblk0p2) in there. Just leave out modemst1 (mmcblk0p13) and modemst2 (mmcblk0p14).
And also you could flash any modem.bin and NON-HLOS.bin (apnhlos) you want since they don't have roll-back protection unlike (aboot, tz etc).
Just to confirm...
This is for the dev (Developer) edition of the SM-900V-dev.
It will NOT work on retail SM-900V.
Has anyone tried this on a retail box yet?
imaverik said:
This is for the dev (Developer) edition of the SM-900V-dev.
It will NOT work on retail SM-900V.
Has anyone tried this on a retail box yet?
Click to expand...
Click to collapse
Good call. Glad I specified already in the thread heading this was for the Dev edition
Sent from my SM-G900V using XDA Premium 4 mobile app
imaverik said:
This is for the dev (Developer) edition of the SM-900V-dev.
It will NOT work on retail SM-900V.
Has anyone tried this on a retail box yet?
Click to expand...
Click to collapse
And no one with a retail unit can try it because the bootloader is locked and non signed Samsung odin packages are rejected.
Sent from my SM-G900V using XDA Premium 4 mobile app
The system.img file might need to be named system.img.ext4. But good job! This will come in handy with a DevS5...I know packages like this have been extremely helpful for those with DevS4's
added ext4 partition to system.img by performing a new data dump with the proper extension. Uploading now. Then Good to go
das7982 said:
added ext4 partition to system.img by performing a new data dump with the proper extension. Uploading now. Then Good to go
Click to expand...
Click to collapse
Is it up yet? or updated? thanks a millie
This worked fine flashing through odin, thanks for posting...
If the S5 Odin ever becomes available you can theoretically steal its recovery.img file and bundle it with this package. It should be the same recovery file for both dev and consumer S5's. Someone prove me wrong?
Sent from my DROID RAZR using Tapatalk
Skeetch79 said:
If the S5 Odin ever becomes available you can theoretically steal its recovery.img file and bundle it with this package. It should be the same recovery file for both dev and consumer S5's. Someone prove me wrong?
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
Look in my link in the OP. I posted the stock recovery which works on every LTE model
Follow me @Bash_array
das7982 said:
Look in my link in the OP. I posted the stock recovery which works on every LTE model
Follow me @Bash_array
Click to expand...
Click to collapse
How do we flash the recovery image, I open Odin but it does not show me this file
das7982 said:
Look in my link in the OP. I posted the stock recovery which works on every LTE model
Follow me @Bash_array
Click to expand...
Click to collapse
My bad! LOL. Great work!
Sent from my DROID RAZR using Tapatalk
razzrmaxx said:
How do we flash the recovery image, I open Odin but it does not show me this file
Click to expand...
Click to collapse
I can make an odin flashable file for the recovery. Do you want just the stock recovery? Also on the play store there is an app called flashify,. You can use this app to flash recovery img files straight from your phone. Works great
Follow me @Bash_array
Thanks for this, worked great!
slydog43 said:
Thanks for this, worked great!
Click to expand...
Click to collapse
Good deal. Glad it was useful to you
Follow me @Bash_array
das7982 said:
Good deal. Glad it was useful to you
Follow me @Bash_array
Click to expand...
Click to collapse
I tried flashing GS5 file in JODIN on Mac and says it was corrupt. Re-downloading file again to computer should be done in hopefully 1 days time. Have to use an open wifi neighbors connection. I got stuck in custom recovery due to me forgetting the reactivation lock is enabled in settings so for now im stuck with no options to boot.
I have a Nexus 5 that has been rooted, unlocked bootloader and I deleted some of the system apps (cant's remember which). I received the OTA update for the 4.4.3 update few says back. Clicked the update, after the download process went through, the phone restarted to install. But then my phone just went dead, it popped up a dead android with the word "error" underneath it x-P.
I know the problem has to do with me uninstalling system apps so is there anyway for me to update to 4.4.3 without wiping my data, if not, I have no problem doing it anyway (nothing too important on my nexus...) Thanks.
Download the factory images of 4.4.3 and flash system, bootloader, recovery and radio.. Doing so will not wipe your data!
- Sent from an IceCold Hammerhead!
danny2146 said:
I have a Nexus 5 that has been rooted, unlocked bootloader and I deleted some of the system apps (cant's remember which). I received the OTA update for the 4.4.3 update few says back. Clicked the update, after the download process went through, the phone restarted to install. But then my phone just went dead, it popped up a dead android with the word "error" underneath it x-P.
I know the problem has to do with me uninstalling system apps so is there anyway for me to update to 4.4.3 without wiping my data, if not, I have no problem doing it anyway (nothing too important on my nexus...) Thanks.
Click to expand...
Click to collapse
Put your phone in bootloader mode and flash the 4.4.3 system img you'll be fine:good:
Download the factory image and flash boot.img, cache.img and system.img, and the new radios.
I would recommend a wipe and do it fresh, but it's up to you.
Edit: 3 replies in the same minute, derp.
Just do this
http://forum.xda-developers.com/showthread.php?p=53109563
Sent from my Nexus 5 using XDA Free mobile app
Lethargy said:
Download the factory image and flash boot.img, cache.img and system.img, and the new radios.
I would recommend a wipe and do it fresh, but it's up to you.
Edit: 3 replies in the same minute, derp.
Click to expand...
Click to collapse
Uhh, that went way over my head, maybe a dumb question but how does one flash img on a android phone? Sorry, I'm still a noob when it comes to these things. (is there a way to do it on a linux computer?)
danny2146 said:
Uhh, that went way over my head, maybe a dumb question but how does one flash img on a android phone? Sorry, I'm still a noob when it comes to these things. (is there a way to do it on a linux computer?)
Click to expand...
Click to collapse
You'll need fastboot setup on your computer. Once you have is setup just go to the link I posted. You just need to double click on the flash-all
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You'll need fastboot setup on your computer. Once you have is setup just go to the link I posted. You just need to double click on the flash-all
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The flash-all.bat/flash-all.sh wipes if I'm not mistaken.
To the OP:
Download the Android SDK and set up fastboot, there are stickied threads for it in the General Section.
Download the factory images and take out boot.img, cache.img and system.img (inside a .zip inside the already compressed file), as well as the radio-hammerhead-m8974a-2.0.50.1.13.img. put them in fastboot directory
Open a cmd prompt in fastboot directory and type (pressing enter after each line, wait for each individual one to complete):
cmd said:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.13.img
Click to expand...
Click to collapse
It might be slightly different on a Linux computer but it should be in the stickies, or search
Lethargy said:
The flash-all.bat/flash-all.sh wipes if I'm not mistaken.
To the OP:
Download the Android SDK and set up fastboot, there are stickied threads for it in the General Section.
Download the factory images and take out boot.img, cache.img and system.img (inside a .zip inside the already compressed file), as well as the radio-hammerhead-m8974a-2.0.50.1.13.img. put them in fastboot directory
Open a cmd prompt in fastboot directory and type (pressing enter after each line, wait for each individual one to complete):
It might be slightly different on a Linux computer but it should be in the stickies, or search
Click to expand...
Click to collapse
Not in the link I gave it's a modified factory image
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Not in the link I gave it's a modified factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Oh, I missed the link. :silly:
No offense to you nor your thread, but it would be better if he gains some knowledge of fastboot/adb.. You know, the usual.
jd1639 said:
Not in the link I gave it's a modified factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
One more question before I do this. I do have to put the supersu zip file in my phone and then flash it after I'm done flashing the factory img, correct?
Lethargy said:
Oh, I missed the link. :silly:
No offense to you nor your thread, but it would be better if he gains some knowledge of fastboot/adb.. You know, the usual.
Click to expand...
Click to collapse
Let's get fastboot setup and we'll go from there
Sent from my Nexus 5 using XDA Free mobile app
danny2146 said:
One more question before I do this. I do have to put the supersu zip file in my phone and then flash it after I'm done flashing the factory img, correct?
Click to expand...
Click to collapse
Yes. because you'll lose root after flashing the factory images. :angel:
Cool, it worked! Now I have to re-root. Thanks a lot for the amazingly quick reply!
danny2146 said:
Cool, it worked! Now I have to re-root. Thanks a lot for the amazingly quick reply!
Click to expand...
Click to collapse
Welcome, if you ever run into issues make a thread in the right section if you can't figure it out yourself, we're here to help. You're welcome to PM me too if you don't think something is worth a new thread although people don't mind if it's in the right section. You seem eager to learn too, which is important. :angel:
Sent from my Nexus 5
Can I just grab the system, boot, and radio images and flash them in fastboot?
Will this retain root and update to 5.0.1?
Sent from my Nexus 5 using XDA Free mobile app
Yes, flash then re-root.
rootSU said:
Yes, flash then re-root.
Click to expand...
Click to collapse
It will take root away I guess?
Sent from my Nexus 5 using XDA Free mobile app
joho5 said:
It will take root away I guess?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Re-root
rootSU said:
Re-root
Click to expand...
Click to collapse
Will i lose custom recovery flashing the system?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
joho5 said:
Will i lose custom recovery flashing the system?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
recovery will be borked. Just flag the twrp image in fastboot
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
recovery will be borked. Just flag the twrp image in fastboot
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Don't think so.
AFAIK, /system/install-recovery.sh and /system/recovery-from-boot.p only exist when OS has gone through an OTA.
If you use a factory image, either to update or reflash /system, those 2 files won't be there - we get to keep our currently installed recovery anyways.
I even go further - when flashing a factory image.. I just skip stick twrp.img in the zip, overwriting recovery.img. Then I use flash-all.sh.
Tip: if you edit the flash-all script and remove the `-w` argument from the `fastboot update filename.zip`, it won't flash user data.img.
This what I did. Download Google factory 5.0.1 image. Unzip. Edit flash-all.bat and remove the "-w" flag for the one command it's found for. Run the edited .bat file. It'll lose root, twrp, but it'll retain data so just flash the recovery over again after the initial flash finishes, then go into twrp to flash SuperSU again and custom kernel if wanted
Sent From Lollipopified Bacon Goodness!
Make sure you flash SU B4 boot or you will loose root.
howard bamber said:
Make sure you flash SU B4 boot or you will loose root.
Click to expand...
Click to collapse
You can just flash it later.
Can you validate/comment on my process?
Looking at this thread, I should be able to perform an update with the factory image without having to return to stock. Can those with a little more experience validate the steps I have below or recommend slight modifications? I was hoping to just flash a rooted/flashable Factory 5.0.1 image, but I don't think anyone has created one yet (if I just missed the ROM, please point me in the right direction).
Steps to Update to 5.0.1 while keeping Files/Root/TWRP
1 - Download Factory Image
2 - Modify flash-all.bat and remove the -w option
3 - Add twrp.img to the Factory image
4 - Fastboot Flash flash-all.bat
6 - Boot system
7 - Possibly have to re-flash SU from TWRP (this isn't a big deal either way)
As always, thanks for all the help here!
BigKenW said:
Looking at this thread, I should be able to perform an update with the factory image without having to return to stock. Can those with a little more experience validate the steps I have below or recommend slight modifications? I was hoping to just flash a rooted/flashable Factory 5.0.1 image, but I don't think anyone has created one yet (if I just missed the ROM, please point me in the right direction).
Steps to Update to 5.0.1 while keeping Files/Root/TWRP
1 - Download Factory Image
2 - Modify flash-all.bat and remove the -w option
3 - Add twrp.img to the Factory image
4 - Fastboot Flash flash-all.bat
6 - Boot system
7 - Possibly have to re-flash SU from TWRP (this isn't a big deal either way)
As always, thanks for all the help here!
Click to expand...
Click to collapse
Give it a try. I'm not sure that the twrp image is going to work. But the worst case is you'll still have the stock recovery after you boot. You'll lose root in any case and will have to flash supersu in the custom recovery
Sent from my Nexus 9 using XDA Free mobile app
BigKenW said:
Looking at this thread, I should be able to perform an update with the factory image without having to return to stock. Can those with a little more experience validate the steps I have below or recommend slight modifications? I was hoping to just flash a rooted/flashable Factory 5.0.1 image, but I don't think anyone has created one yet (if I just missed the ROM, please point me in the right direction).
Steps to Update to 5.0.1 while keeping Files/Root/TWRP
1 - Download Factory Image
2 - Modify flash-all.bat and remove the -w option
3 - Add twrp.img to the Factory image
4 - Fastboot Flash flash-all.bat
6 - Boot system
7 - Possibly have to re-flash SU from TWRP (this isn't a big deal either way)
As always, thanks for all the help here!
Click to expand...
Click to collapse
Just to make sure you understand what you're saying.
At step 3..
The twrp img file you download from their website needs to be renamed recovery.img and placed inside the update-rest-of-filename.zip, overwriting the one that's there already (yep, the stock recovery).
You got everything else right.
a maguro wrote this.
Or just type "fastboot flash recovery twrp.img" once you do the rest but skip step 3 cuz that is done with the command I wrote at the end of the process before you boot up.
1. Edit flash-all.bat to remove -w option
2. Run it to flash everything.
3. "Fastboot flash recovery twrp.img" (rename the twrp file you download to match twrp.img cuz it'll be a long name when you download it
4. In fastboot scroll to recovery, boot into it, it will boot into twrp
5. Flash SuperSU latest version from twrp (so make sure u have this on ur sdcard somewhere like in the downloads folder for example before u begin process
6. Clear dalvik and cache and reboot into lollipop. First boot may take a few min like 5 to 10
Sent From Lollipopified Bacon Goodness!
Didn't try it
I appreciate the tips. Just before I was about to attempt this, I saw Vomer posted a flashable image. I decided to go that route. Looks good so far.
BigKenW said:
I appreciate the tips. Just before I was about to attempt this, I saw Vomer posted a flashable image. I decided to go that route. Looks good so far.
Click to expand...
Click to collapse
And we were all in suspense to see how it worked out
Sent from my Nexus 9 using XDA Free mobile app