Hello, I flashed PA 4.4.4 on my i9250 and now I wanted to go back to 4.3. Unfortunately I have a problem because my 4.3 backup isn't visible anymore, directories are messed up by 4.4.4. Found a way to make it visible (had to put an old backup to /data/media/clockworkmod/backup/) but I get an error while trying to restore it. I even flashed my previous cwm and installed cm 10 (the one that I've got my last backup from) but now all i get is a bootloop... I think it's caused by messed directories. How to get rid of those f***ing 0 emulated location?
1. Download JB factory image for your NExus from here: https://developers.google.com/android/nexus/images
2. In the recovery make swipe data/factory reset
3. power off and boot into fastboot mode...
3. Flash system partition through fastboot. (You need Fastboot drivers for Windows..) (system.img):
fastboot flash system system.img
and flash boot.img :
fastboot flash boot boot.img
4. Boot.
Nb. You have to extract the img files from the zip package.. if you want you can use flash all batch file (.bat) or script file (.sh) (depends of the OS...) but if you use it, then it'll flash everything automatically and wipes everything from the phone.
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
casioman1 said:
Hm I hoped that will do without going back to stock. I suppose this operation will relock my bootloader?
Click to expand...
Click to collapse
Only fastboot oem lock command locks your nexus's boot loader.
About "0" and some other directories, these are new on JB 4.2 or 4.3... you can remove them but it's useless... so I recommend to keep them.. 0 is like the current user,, for e.g 3 is the second user (multi user)...
CWM backups: I am not really sure... you can remove md5 stuff and maybe recovery lets you flash the files.. Also use the recovery with what you made the backup if newer CWM recoveries won't flash it
Hell yeah! Finally got it done. This it how:
1. flashed an old recovery (the one that I've got my last backup from) but still got a bootloop with an old cm10.
2. installed the newest working wersion of CM just to put my backup into different directory and make it visible (make sure you copy both folders with a date of your backup AND blobs because without the latter one it won't restore giving you an error)
3. voila, you've got a fully restored system
Thanks Carlos_Manuel for your help
Related
Hey together,
I hope you can help me. I have a strange problem.
Chronologically:
1) I had been running Xylon JB 4.2 ROM for 2 or 3 months on my GNexus. Everything was fine. Except that I noticed over the time a slight lag all over the OS. The general reaction time was not so fast as it should be (Note: My phone has not that memory unit which causes those extreme lags I read about somewhere in this forum).
2) So I decided to go back to stock. I did a full wipe and flashed a JOP40D 4.2.1 Odex Rooted Busybox FactoryImage which I took from this forum (don't know which thread). The good: Android was very fast again. The bad: Immediately after flashing it I encountered problems. At every boot I got the "Android is upgrading... XX of XX apps..." screen, even after a separate dalvik wipe, and really at every boot (not just the 1st after dalvik wipe). Furthermore, I noticed that some apps behave strange, for example Play Music couldn't play any music from my internal storage which worked fine under Xylon. Plus, system settings like the ring sound were not saved so that after reboot there was set a different ring tone. I thought, well, maybe something went wrong when I restored my apps via TB (apps via update.zip, data via TB app).
3) Due to the strange behaviour I decided to carry out a complete wipe via TWRP. I mean really a full storage wipe, this sort of wipe when TWRP warns you and says this was not needed most of the time. I thought it couldn't be wrong to wipe everything that can be wiped to fight the problem. After that, I flashed 4.1 factory image via the GNex Toolkit because there was no rom zip anymore on the internal storage. (4.1 because the Toolkit couldn't download any newer image correctly). Back in Android, I copied bigxie's JOP40D deodex ROM on the storage and flashed it (full wipe before). And yes I updated the SuperSU binaries as bigxie told. This time I didn't use Titanium Backup for restore, but installed the apps directly from Play Store, the cleanest method. And AGAIN, the phone is showing some strange behaviour! This time no problems with dalvik cache, but with some other part of the storage as it seems. Some apps refuse to start ("app XYZ was closed" - report - OK), even after uninstall and reinstall from Play Store, for example Öffi, DB Navigator, mehr-tanken which worked fine under Xylon. the Facebook app doesn't save data correctly. At nearly every start it asks me if I want to find friends (normally only 1st start). But other Facebook app settings (notification etc.) are saved correctly. Strange, isn't it?? Wipe cache and dalvik cache didn't change anything.
I'm completely desperate. What can be the cause for the strange behaviour? Maybe the storage or something broken?
I've flashed ROMs so often with several Android devices, so I think I'm not such a complete noob. But what could have happened?
I beg you to answer if you have any suggestions what I can try.
I could kick myself for touching my Xylon setup which had worked fine (just slightly slow), even considering that I'm facing my exams in 6 weeks and should learn day and night...
Thanks in advance!!!
it seems like everytime i read about someone having some kind of strange anomoly, its someone whos using a toolkit (not trashing you, but i keep seeing the correlation); which is why i havent touched them, plus fastboot is more fun. anyways this is how i would go about it, and get your stock image ready.
fastboot format system
fastboot format userdata
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot rebooot-bootloader
fastboot flash userdata userdata.img
fastboot reboot
try that, just make sure you have adb and fastboot set up right. its the most basic failsafe for sure method to get to 100% stock without any trash left behind on your phone
Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?
staud said:
Hey, thanks for your detailed suggestion!
I'm not sure if the problem can be toolkit related as I didn't use the toolkit for the first flash (step 2 in my first posting). But nevertheless, I'll follow your suggestion as soon as I can manage it.
I have not much experience with fastboot as the only thing I did with fastboot was flashing custom recoveries.
So just to be safe I'd like to know what you mean exactly by
1) fastboot flash boot boot.img
2) fastboot flash system system.img
3) fastboot flash userdata userdata.img
I downloaded the JOP40D factory image and unzipped the RAR file. It contains:
bootloader-maguro-primelc03.img, flash-all.bat, flash-all.sh, flash-base.sh, image-yakju-jop40d.zip, radio-maguro-i9250xxlh1.img
Shall I take the boot.img, system.img and userdata.img from the zip file?
What shall I do then with all the other files except the zip file?
Click to expand...
Click to collapse
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot. for example, the command fastboot flash boot, is the command to flash the boot image. the second part is the file name you want it to flash, so fastboot flash boot boot.img. you shouldnt need to flash the bootloader or radios if they are working correctly. if you want to anyways, check efrant's nexus guide on here, i forget the commands to differentiate between the two different radios when you flash them.
if you do the bootloader and decided to erase and flash instead of just flashing over it, DO NOT use the command fastboot reboot-bootloader until after you flash the bootloader. otherwise it will try to reboot into a bootloader that doesnt exist, if that makes sense. someone correct me if im wrong about this part.
username8611 said:
what all is in the file image-yakju-jop40d.zip? you should have boot.img, recovery.img, system.img, userdata.img. if those are all in there, you can extract them to the folder you use to flash from in fastboot.
Click to expand...
Click to collapse
Yeah, those were in the zip. I followed your fastboot how-to within the last 10 minutes and it worked so far as the new stock Android has just booted. By now I can't tell if the strange things have really disappeared. I'll see how things go within in the next hours and days and repost if I encounter again any problems. By now - thanks dude! :good:
EDIT: You wrote reboot with 3 o once. I noticed it but maybe you might wish to correct that if some other desperate and help-searching guy follows your how-to
EDIT2: After 3 days I haven't encountered any strange behaviour. But I didn't root it again or any other modding stuff. Just stock Android. For the moment I'm happy that it runs without problems and I won't touch it again until my exams are done. It seems to me that your method was successful. Thanks again!
hi
i already unlock the bootloader, install custom recovery TWRP, and done a backup
i also copy my backup to PC
now i'm confuse
- i need to root the phone or can i just flash the new room?
- if i need to root the phone i found an italian guide on 4.0 and attach file, can i use that? i have 4.1.1 on mine now
i'm not interested to have HTC stock with root but what i want is to install MIUI ROM
this is the only guide i found in english that explains how to install the rom
external link (i can't post it) miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
what i understand is:
- boot my device power + menu down, to see the FASTBOOT USB i have to select FASTBOOT
- flash the boot.img
- press the power button once (HBOOT i guess), click volume down, highlight recovery & press power
- Flash the downloaded ROM via recovery normally and it followup at this link
external link (i can't post it) miuiandroid.com/community/threads/how-to-update-upgrade-miui.15424/
i need to copy the img rom in SD ROOT before starting with all this process
- now i need to Wipe data/factory reset, Cache Wipe & Dalvik Cache Wipe in all tutorial i found this is done with clockworkmod
in TWRP under menu WIPE i guess are System, Cache, Dalvik buttons
after that i'm note sure if i need to flash italian language, if i don't need and i can just download it later i tihink is not a big deal
unless is all in chinese
is the metod correct?
do i have to copy ROM file in .zip format as i download?
here where i found ROM
from official site grey button miui.com/download-7.html
OR
from UK web site miuiandroid.com/community/threads/3-4-28.20232/
the boot.img is here
point 3 miuiandroid.com/community/threads/installing-the-htc-one-x-required-s-on-steps.16592/
i'm not sure if would be better to use clockworkmod, since most tutorials use that..
thanks
Doesn't matter which recovery you use. Yes just place the zip file on your sd card. Flash boot.img as you already said. Perform a full wipe and then flash the Rom zip. Reboot and its done.
The Roms are pre-rooted so you dont need to worry about that. Italian language should be included i guess.
Sent from my HTC One X using xda app-developers app
Heres what i do :
1) Put Rom.zip on SD card
2) Put boot.img in fastboot folder
3) fastboot erase cache
4) fastboot flash boot boot.img
5) fastboot erase cache
6) Reboot into recovery
7) Full wipe (except sd card)
8) Install rom
9) Enjoy new rom
Andy
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
al404 said:
i did my first mess but fortunally i could restore since i had copy the backup on my mac too
i don't know what went wrong but this is what happened:
- i did how was told before, but actually i download boot.img and rom from 2 different sites
- after reboot it didn't move from first screena waited for 15 minutes almost, so i did reboot in recovery tri to wipe but nothing happened
- so i decide to restore... but it did boot even if it was successful
- i thought that if i flashed the boot.img first time i may need to do it again, i found boot.emmc.win, rename it to boot.img, flash it and then i restored successfully
:victory:
now, to try a different rom i need to restore (maybe is safer)? can i copy the rom from recovery or fastboot?
what can it be wrong with my miui rom? could it be boot.img and rom file mismatch? can't find where to download both
Click to expand...
Click to collapse
extract the boot image from the rom you are going to use
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
1st u didn't mention which phone u r using
2nd dn't get confuse while downloading rom n .img file
Type in google
(Ur phone model) android development xda
U'll find all the stuffs related to ur phone
So try this 1 n remember before updating or rooting or anythg related to ur which can mess ur phone or can brick ur phone
I suggest u read twice the thread n procedures n also check thrice the stuff which u gonna need to perform ur act.
Sent from my GT-N7100 using xda premium
al404 said:
ok, i tryed again but now it get stack on Mi black screen
i waited 8 minutes but nothing happens, i also tried to wipe cache and davik, nothing happens
at list i get to black Mi screen
do i need to delete the boot.img from ROM zip?
what could it be?
Click to expand...
Click to collapse
i would try a different rom for now, viperx perhaps. and the boot image is in the rom zip, extract the boot img from the rom and put it in your fastboot folder then copy the rom to your sdcard. once you have done that, fastboot erase cache, flash the boot image, fastboot erase cache again, then back into recovery, wipe cache and dalvik just to be sure then use recovery to flash the rom and hey presto. all of the above is assuming you have the one x international tegra 3
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
al404 said:
I have htc one x european terga 3, as far as I know mini is only for tegra 3
what you describe is exactly what I did:
- I leave the rom zip ad it is, I didn't remove boot.imf that I extract, correct?
- when I flash I hit hoot fastboot, connect USB and fastboot change in fastboot USB, to go back I select Hboot and and hit power, prom there recovery
- I did unlock bootloader but did not get rooted my phone, could it be that?
Click to expand...
Click to collapse
read this post. at least twice!! http://forum.xda-developers.com/showthread.php?t=2069904 do not do the "unlock bootloader" section as you already did that
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
al404 said:
@nogotaclue sorry i read so many, and some of them sayed that root was not necessary if you flash a new rom, other sayed it could still be necessary... now i rooted with the app and did a new backup that i'm coping on PC
reading further it says: to wipe, install rom, and flash boot.img after
"Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it."
Click to expand...
Click to collapse
yes you can do it that way, i usually flash first but sometimes it does not work, so just flash it last as it says in the tutorial
after root, with the same steps, the ROM starts... but
touch screen is not working :crying:
now i'm gonna look arond to see if i found some post about that
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
al404 said:
this (kernel patch) solved my last issue
http://miuiandroid.com/community/threads/hox-miui-v5-official-release.20215/page-2
Click to expand...
Click to collapse
So everything working now ?
Sent from my underpants using Daz and Lenor summertime
YES :good: without that path touchscreen wasn't working :victory:
hope is not going to mess all up with first update
I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Aremisalive said:
I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Click to expand...
Click to collapse
I can't actually find a KTU841 zip on the Google Devs page, also stock images from said source are typically not .zip files, they are .tgz images. (https://developers.google.com/android/nexus/images). The reason you can't OTA update is because you rooted your device, once unlocked and rooted you need to sideload updates manually, a small price you pay for wanting that bit more.
To me it sounds as if a factory reset may be your best option in this case, that is certainly what I would do at this juncture. You can still connect your device to your computer and back up all your stuff before you wipe it though.
Aremisalive said:
I have not had a lot of experience with SDK tools like adb and fastboot, but I have used them to Root my Nexus 7 (2013) with no problems. But now I am not able to update my Nexus from Kit kat 4.4.2. I have had no problems updateing before, and have not had problems rooting after updating. But when I try to update via the OTA update, it fails every time. I had the TWRP Recovery, and had no problems updating. When this update failed I tried useing the ClockworkMod recovory, but the update also failed. I tried to manually update useing the downloaded razor-ktu841.zip, and the platform tools fastboot. If I run the flash-all.bat, it will write the bootloader, and then restart the bootloader. After that Fastboot.exe crashes. I used Fastboot to flash the stock recovery for my device, and that worked flawlessly. But again, both the OTA update and updating manually failed. If I try to just update useing "fastboot -w update image-razor-ktu84l.zip" Fastboot.exe also crashes. I would leave my Nexus on 4.4.2, but I am having occasional issues with the touch screen, and frequent problems with the Gyroscope and Accelerometer that I hope will be fixed by updating. They will just stop working, and only a restart fixes them. I am compleatly stock as far as roms go. I stuck with stock android. I also believe I have the stock kernel as well, seeing as how I never touched it. I would rather not factory reset my tablet, because I have a lot of stuff on it. That would be a last resort for me.
Any help would be much appreciated.
Click to expand...
Click to collapse
Sounds like you need to reinstall/update the SDK. You're missing a .dll or something. I know I have in the past deleted more than what I should have when cleaning out the platform tools folder after flashing images. If you run the flash-all.bat it will COMPLETELY wipe your device including whatever is in storage. You can modify the flash-all.bat with a text editor and then be able to use it without it doing a complete wipe. Open the flash-all.bat with notepad (I use editpad lite) and remove the -w from the text. Removing the -w will keep the flash-all.bat from flashing the userdata.img which is inside the image zip which is what wipes the device. The flash-all.bat will flash the stock recovery so any custom recovery will have to be reflashed if you use the bat file. Personally... after fixing your sdk install I would pull the boot.img and system.img from inside the image zip and put those in your platform tools folder so that you can fastboot flash them. Download a custom recovery (I use TWRP) and rename it to something shorter, put it inside your platform tools folder so that you can fastboot flash it also. Download the supersu installable zip and put it in your device storage. The bootloader image does not need to be flashed because it has not changed from 4.4.2 to 4.4.4.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp.img
Use the buttons on device to boot into recovery. Install the super su zip. Then go to advanced wipe, wipe cache and dalvik. Reboot system. "IF" you run into any problems after updating you can do a factory reset from inside TWRP and it will not wipe your storage. Of course, doing a factory reset from your devices Settings/Backup & reset will wipe everything.
purephysics said:
I can't actually find a KTU841 zip on the Google Devs page, also stock images from said source are typically not .zip files, they are .tgz images. (https://developers.google.com/android/nexus/images). The reason you can't OTA update is because you rooted your device, once unlocked and rooted you need to sideload updates manually, a small price you pay for wanting that bit more.
Click to expand...
Click to collapse
The OP was correct. If you unzip the tgz far enough you will see:
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-ktu84l.zip
Inside image-razor-ktu84l.zip you will see the rest of the images:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Being rooted will not prevent you from being able to download and use an OTA like you can if not rooted. It's what you do after you are rooted that will make an OTA fail, a lot of the time even if you sideload it. Custom kernels, ANY mods to system files can and usually will throw an unexpected contents error or some other kind of error. The smaller the OTA is the more likely it will work, I wouldn't count on it but it is possible. If there are no modified files that the OTA is trying to update the OTA could work. Fact is, a couple of the KitKat updates were VERY small and I was able to get the OTA to work just fine (without sideloading) and I use a custom kernel, recovery, hosts file, media_profiles.xml, fonts, bootanimation and ui/audio sounds. I almost always fastboot flash the needed images separately but for grins tried those two small OTA's. Rarely do I even bother with an OTA.
Works!
wantabe said:
Sounds like you need to reinstall/update the SDK. You're missing a .dll or something. I know I have in the past deleted more than what I should have when cleaning out the platform tools folder after flashing images. If you run the flash-all.bat it will COMPLETELY wipe your device including whatever is in storage. You can modify the flash-all.bat with a text editor and then be able to use it without it doing a complete wipe. Open the flash-all.bat with notepad (I use editpad lite) and remove the -w from the text. Removing the -w will keep the flash-all.bat from flashing the userdata.img which is inside the image zip which is what wipes the device. The flash-all.bat will flash the stock recovery so any custom recovery will have to be reflashed if you use the bat file. Personally... after fixing your sdk install I would pull the boot.img and system.img from inside the image zip and put those in your platform tools folder so that you can fastboot flash them. Download a custom recovery (I use TWRP) and rename it to something shorter, put it inside your platform tools folder so that you can fastboot flash it also. Download the supersu installable zip and put it in your device storage. The bootloader image does not need to be flashed because it has not changed from 4.4.2 to 4.4.4.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp.img
Use the buttons on device to boot into recovery. Install the super su zip. Then go to advanced wipe, wipe cache and dalvik. Reboot system. "IF" you run into any problems after updating you can do a factory reset from inside TWRP and it will not wipe your storage. Of course, doing a factory reset from your devices Settings/Backup & reset will wipe everything.
The OP was correct. If you unzip the tgz far enough you will see:
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-ktu84l.zip
Inside image-razor-ktu84l.zip you will see the rest of the images:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Being rooted will not prevent you from being able to download and use an OTA like you can if not rooted. It's what you do after you are rooted that will make an OTA fail, a lot of the time even if you sideload it. Custom kernels, ANY mods to system files can and usually will throw an unexpected contents error or some other kind of error. The smaller the OTA is the more likely it will work, I wouldn't count on it but it is possible. If there are no modified files that the OTA is trying to update the OTA could work. Fact is, a couple of the KitKat updates were VERY small and I was able to get the OTA to work just fine (without sideloading) and I use a custom kernel, recovery, hosts file, media_profiles.xml, fonts, bootanimation and ui/audio sounds. I almost always fastboot flash the needed images separately but for grins tried those two small OTA's. Rarely do I even bother with an OTA.
Click to expand...
Click to collapse
Thanks for your help, after re-downloading the SDK, and image (just to be safe) I was able to flash the boot, system, and recovery with no problems. It upgraded me to 4.4.3! I then was able to do an OTA update to 4.4.4 and then rooted it by installing the SuperSU installable zip with TWRP with no problems. Thank you very much!
Thanks to all the sources for unbricking my P930. However, I have a small problem.
After repeated failures at reverting back to Gingerbread, I used bootloader for ICS to gain access.
It turns out that the ROM I want to use will not load unless I have GB boot image.
Heres my 4 questions, I have downloaded the boot, baseband, firmware, recovery and system images from
Machzelets' tutorial. My phones card reader is not working. 1. Can I push those images to /data/media or
some other directory and dd the files as Machzelets' tutorial describes? 2. Will installing the system.img erase
those files? 3. Also, can I push one file at a time then delete it and go on to the next. 4. And, will CWM be okay to use instead of
factory stock recovery?
I am running Mokee right now but I want to go back to Dirty Unicorn.....
Thanks to everyone again. Cheers,
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone