Hey guys,
After rooting, I seem to have removed some bloatware that I wasn't supposed to, messing up my JB build. I forgot to do a nandroid backup (is there even a way to do it on the Razr M), I was wondering if there was a way I could restore the stock factory ROM, using RSDLite or something. Thanks.
bosun120 said:
Hey guys,
After rooting, I seem to have removed some bloatware that I wasn't supposed to, messing up my JB build. I forgot to do a nandroid backup (is there even a way to do it on the Razr M), I was wondering if there was a way I could restore the stock factory ROM, using RSDLite or something. Thanks.
Click to expand...
Click to collapse
Yes, there are fast boot file that u can use.
Sent from my XT907 using Tapatalk 2
Using the firmware here: http://forum.xda-developers.com/showthread.php?t=2017200, I tried restoring via RSDLite, however it won't recognize my phone (fastboot mode, RSDLite 6.14, latest Motorola drivers). Is there any way to fix this, or use the terminal to push the package to the phone?
Related
Guys i need your help
History:
1. bought the phone with froyo (phone is atrix 4g att)
2. updated over-the-air to gingerbread
3. rooted
4. installed clockworkmod
5. unlocked bootloader
6. backed up stock rom
6. installed cyanogenmod 7 beta with android recovery (update.zip)
Now I want to get back to gingerbread 2.3.4, so can i just restore it via clockworkmod restore or there is some other way?
And if i just restore my backup, is it safe for future OTA updates?
PS: i did spend my time searching and reading xda forums but i am not sure what to do because english is my 2nd language and i don't understand everything, i love my atrix and don't wan't to brick it
Thanks
Just flash one of the fruitcake roms. They're simple update.zip's and completely stock http://forum.xda-developers.com/showthread.php?t=1163009&highlight=fruit
grave101 said:
Just flash one of the fruitcake roms. They're simple update.zip's and completely stock http://forum.xda-developers.com/showthread.php?t=1163009&highlight=fruit
Click to expand...
Click to collapse
System and boot version only? What happened with webtop after flashing to cm7, is it still in phone?
What about some other rom, alien or aura, is the same procedure as for cm7 via android recovery?
You backed up your previous rom.....restore it.
carlharsch said:
You backed up your previous rom.....restore it.
Click to expand...
Click to collapse
And if i want to try some other roms, i can do it safely via android recovery?
elvirr said:
And if i want to try some other roms, i can do it safely via android recovery?
Click to expand...
Click to collapse
flash either CWM packages or fastboot flash of system / boot partitions.
those are safe.
xploited said:
flash either CWM packages or fastboot flash of system / boot partitions.
those are safe.
Click to expand...
Click to collapse
OK, works great, thank you
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
ravenofdoom said:
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
Click to expand...
Click to collapse
The stock Android recovery cannot make entire system (NANDROID) backups like TWRP or CWMR can. If your looking to re-install stock Android 4.2.2 for the Nexus 10 you can download and flash the Nexus 10 factory image from here (I would recommend taking a look at this great guide if your are unfamiliar with how to flash factory images). If you just want to reflash the Nexus 10 stock recovery you can download it from here, boot into fastboot mode and then flash it with the following command:
Code:
fastboot flash recovery path/to/recovery-stock-manta.img
After it completes you can reboot into recovery mode and you should now have the stock Nexus 10 recovery image installed. For flashing the stock recovery you should try and match it to the Android version so if your on Android 4.2.2 try and flash the recovery.img that was pulled from the Android 4.2.2 factory image. However usually you can get away with flashing 4.2 or 4.2.1 version of the stock recovery.img as it is unlikely that anything major changed with the stock recovery image in those small incremental Android updates.
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
abdel12345 said:
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
Click to expand...
Click to collapse
Correct flashing stock recovery won't make you loose any data. But as always when your flashing anything and if you have even the slightest hesitation backup any data you wouldn't want to loose.
Sent from my SCH-I535 using xda premium
Alright thanks man. I already used my 8 for today but ill thank you tomorrow and ill back up my apps with titanium backup
OK what is the command to use to flash because the one from the previous page didn't work it said something about not finding it or something are there any drivers that need to be installed or something I'm missing? I connected it to my CPU and turned it on while holding power and volume and it went menu where you see tablet info? Any help please
Sent from my Xperia Play (r800x)
ravenofdoom said:
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Click to expand...
Click to collapse
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
abdel12345 said:
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Cool. :thumbup:
Sent from my Nexus 10 using Tapatalk HD
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
abdel12345 said:
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
Click to expand...
Click to collapse
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
OK I'll try yhat
Sent from my Xperia Play (r800x)
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
Hello!
I have just got a new LG G2!
I want to root it, but I'm a little bit confused atm:
1) Rooting the device using IORoot does not change the kernel or recovery, does it? (I'll be rooted runnig stock and won't be able to flash stuff)
2) If I want to create a nandroid backup, I have to flash first CWM/TWRP. So how can I make a nandroid backup for my current unrooted and runnig stock phone?
3) Can I backup my EFS files without a custum recovery (with root only)?
4) Is that correct that after each rom I flash, the phone needs to be rooted again?
Thanks!
1. Yes
2. You use the cwm. Or twrp to make the backup.
3. Not sure, have always been rooted sui never looked for a way to do that.
4. No, I've never had to reroot after installing any rom.
Sent from my LG-D800 using Tapatalk
unroot
Is there a way to unroot and leave no evidence that the phones been rooted. Im planning to return it and get another one. THanks in advance
I rooted the phone, everything was going good. I was playing with Exposed and I wanted to remove soft keys. I found a post to edit build.prop and I did not back up build.prop before i tried to edit it and all went all from there.
Now When i turn it on i get it booted up but it says unfortunately androidsystem.ui has stopped and wont go any farther,
I am running 4.4.2 stock rom, After this I did a factory reset hoping this to fix the problem...This did not fix it lol.
I am afraid I can not ADB it now as I do not have developer options and USB debugging....
Anyway to edit Build.prop from the computer?
if not how do i fix this?
Thank you!
Bobert the great said:
I rooted the phone, everything was going good. I was playing with Exposed and I wanted to remove soft keys. I found a post to edit build.prop and I did not back up build.prop before i tried to edit it and all went all from there.
Now When i turn it on i get it booted up but it says unfortunately androidsystem.ui has stopped and wont go any farther,
I am running 4.4.2 stock rom, After this I did a factory reset hoping this to fix the problem...This did not fix it lol.
I am afraid I can not ADB it now as I do not have developer options and USB debugging....
Anyway to edit Build.prop from the computer?
if not how do i fix this?
Thank you!
Click to expand...
Click to collapse
First off, brick means it's as functional as a fired clay brick.
Second. ADB from recovery. If you don't have a custom recovery, factory reset.
khaytsus said:
First off, brick means it's as functional as a fired clay brick.
Second. ADB from recovery. If you don't have a custom recovery, factory reset.
Click to expand...
Click to collapse
I don't think a factory reset would help since it only wipes data and cache. He said he already tried one without success.
If you have a custom recovery installed, you have a couple of options. If adb is working, you can pull/push a fixed build.prop. Or you could find a stock build.prop and create a flashable zip for it.
If you don't have a custom recovery, as far as I know you're pretty much stuck having to flash a factory image, which means you'll lose all your data because your internal storage will be wiped.
detonation said:
I don't think a factory reset would help since it only wipes data and cache. He said he already tried one without success.
If you have a custom recovery installed, you have a couple of options. If adb is working, you can pull/push a fixed build.prop. Or you could find a stock build.prop and create a flashable zip for it.
If you don't have a custom recovery, as far as I know you're pretty much stuck having to flash a factory image, which means you'll lose all your data because your internal storage will be wiped.
Click to expand...
Click to collapse
I do not have a custom recovery as I rooted 4.4.2 and as far as I know you can not have recovery with 4.4.2 root unless you downgrade to 4.2 first, root then update, Correct?
I was wondering, Can i install custom recovery now?
Keep in mind this is my second LG G2, The first one I COMPLETELY bricked it and it wont power on, no LG image, No charge, no download mode nothing. I do not want that again as it is a paper weight now lol.
http://forum.xda-developers.com/showthread.php?t=2432476
Would this be the process I would go with?
Thanks to everyone for the help....I hope to have my phone back up and running soon!
Bobert the great said:
I do not have a custom recovery as I rooted 4.4.2 and as far as I know you can not have recovery with 4.4.2 root unless you downgrade to 4.2 first, root then update, Correct?
I was wondering, Can i install custom recovery now?
Keep in mind this is my second LG G2, The first one I COMPLETELY bricked it and it wont power on, no LG image, No charge, no download mode nothing. I do not want that again as it is a paper weight now lol.
Click to expand...
Click to collapse
I have the Verizon version so I can't speak for others, but you only need to downgrade to the 4.2 bootloader to install the recovery and then you can go back to the 4.4 bootloader. I used AutoRec which does it all for you automatically. But at this point I don't think you'll be able to flash a custom recovery, as you either need adb access or the ability to install an apk.
Here's the guide for flashing the factory images: http://forum.xda-developers.com/showthread.php?t=2432476
I suggest trying the TOT method first if your variant is supported
Thank you,
I believe I will trade to flash stock rom again and root from 4.4.
Wish me luck.
As i look into the TOT flash procedure I am wondering what Variant the D803 is....
I have a Telus LG G2 and I believe it is the D803....
It is fixed everyone. Thanks to everyone who helped.
Sent from my LG-D803 using XDA Free mobile app
Bobert the great said:
It is fixed everyone. Thanks to everyone who helped.
Sent from my LG-D803 using XDA Free mobile app
Click to expand...
Click to collapse
I had this issue.
http://forum.xda-developers.com/showthread.php?p=52733594
Now I'm in 4.4.2 again but with a custom recovery and backup. Ready to give it a whirl again.