Related
Can anyone provide their stock recovery image from the WiFi-Xoom Jelly Bean JRO03H update? I need it for testing something.
Thanks!
sorry didnt see this earlier
did you get what you needed? having issues here at work and cant upload a recovery.img i have from a nandroid i took on 7/26, not sure if it is 03H though but i will upload it or send you a DropBox link
Yeah I'm good. Thanks though! Out of curiosity, how did you nandroid the stock recovery image? Wouldn't you have had to flash a custom recovery in order to do the android in the first place? As far as I know, the Xoom can't boot a recovery image without flashing...
Sent from my Nexus 7 using Tapatalk 2
well if this nandroid is from when i got it, i first put the US wifi firmware on it from motodev, then used fastboot to flash a CWM recovery, booted into recovery and did a nandroid, then flashed a custom rom...i think thats how i did it
i'll restore the nandroid and see whats what. if it is the stock recovery image (or any other img) then it will overwrite twrp correct?
dodgefan67 said:
well if this nandroid is from when i got it, i first put the US wifi firmware on it from motodev, then used fastboot to flash a CWM recovery, booted into recovery and did a nandroid, then flashed a custom rom...i think thats how i did it
i'll restore the nandroid and see whats what. if it is the stock recovery image (or any other img) then it will overwrite twrp correct?
Click to expand...
Click to collapse
Yep, it'll overwrite TWRP. Chances are 99% that the recovery image in your nandroid will be whatever recovery you used to make the nandroid in the first place.
oldblue910 said:
Yep, it'll overwrite TWRP. Chances are 99% that the recovery image in your nandroid will be whatever recovery you used to make the nandroid in the first place.
Click to expand...
Click to collapse
yep, you're right
i can put the US wifi firmware on it and do all the ota upgrades, would that do it?
Dude don't even go to the trouble. I'm all set. Thanks for volunteering though!
Sent from my Xoom using Tapatalk 2
too late LOL
no worries, helps me learn. how would i get the recovery.img off it now, its all stock. adb pull recovery.img?
dodgefan67 said:
too late LOL
no worries, helps me learn. how would i get the recovery.img off it now, its all stock. adb pull recovery.img?
Click to expand...
Click to collapse
No, you word have to root, then download the Android terminal editor, and dump the recovery image using the UNIX dd command. Not sure of proper syntax off the top of my head..
Sent from my Nexus S using Tapatalk 2
yeah it would be something like this, but have to know the correct partition naming to make it work
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard1/recovery.img
but then i think i have to flash a recovery to root it, have only found one way to root and that is with a flashable zip file. oh well, it was worth the try
Hello, before doing anything I will be glad to know how to backup Kernel and Modem with adb or any other way, is there anyone that could help me!?
Thanks!
Use TWRP or CWM to backup the kernel, you also *need* to backup your EFS just in case it ever gets deleted but I have never once had an issue with that. I dont know of a way to backup your modem but I dont see why it is necessary. You can download any and all modem files online.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
EniGmA1987 said:
Use TWRP or CWM to backup the kernel, you also *need* to backup your EFS just in case it ever gets deleted but I have never once had an issue with that. I dont know of a way to backup your modem but I dont see why it is necessary. You can download any and all modem files online.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
Click to expand...
Click to collapse
I think is a better way to do it by ADB commands, suppose you mess up something when installing TWRP or CWM?... for I think knowing the way with ADB is better.
So then look up the ADB commands for it. If you use ADB though you NEED a computer to fix your phone. Having a flashable recovery kernel on your phone means you can recover any time. If you are so broken that you cant flash a kernel in recovery then you will need far more ADB help than a kernel backup anyway.
EniGmA1987 said:
So then look up the ADB commands for it. If you use ADB though you NEED a computer to fix your phone. Having a flashable recovery kernel on your phone means you can recover any time. If you are so broken that you cant flash a kernel in recovery then you will need far more ADB help than a kernel backup anyway.
Click to expand...
Click to collapse
I have experience with my Samsung Galaxy S2, I'm asking this because this G2 seems a bit more complicated, for example people having bootloops when install TWRP and I want to avoid that...
G2 isnt complicated at all compared to any modern phone, besides a Nexus. As long as you root and flash your first recovery properly then there are no issues. It is all the people being dumb and wanting to use just some app to try and do everything that are having problems. Use ADB to root your phone and use ADB to run loki and flash your recovery and you will have no issues. People are just forgetting about their locked bootloader and needing to use Loki to bypass the lock, then they complain about a screwed up device because they didnt do anything properly.
Flashify, which makes installing recoveries, etc super easy, has an option to back those up.
Barsky said:
Flashify, which makes installing recoveries, etc super easy, has an option to back those up.
Click to expand...
Click to collapse
HOPE THIS WORKS:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
flashing a custom kernel and hopefullly this does the job of backing it and restoring it the original one!!:fingers-crossed::fingers-crossed:
All,
Please help i just download the OTA update on my LG G2 D802 (international version) and perform an update. I was suprise it only boots on Clockworkmod recovery v6.0.4.7. How to resolve this as i can't afford to reformat everything on my phone. Thanks
kolokoy said:
All,
Please help i just download the OTA update on my LG G2 D802 (international version) and perform an update. I was suprise it only boots on Clockworkmod recovery v6.0.4.7. How to resolve this as i can't afford to reformat everything on my phone. Thanks
Click to expand...
Click to collapse
Never accept an OTA with Custom Recovery.
You need to wipe everything and then flash a kdz.
kolokoy said:
All,
Please help i just download the OTA update on my LG G2 D802 (international version) and perform an update. I was suprise it only boots on Clockworkmod recovery v6.0.4.7. How to resolve this as i can't afford to reformat everything on my phone. Thanks
Click to expand...
Click to collapse
if you have not already flashed back to stock and have adb access you can try the following command-
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
I have not yet flash the stock rom. Before attempting to experiment on below, have you tried below procedure?
XxZombiePikachu said:
if you have not already flashed back to stock and have adb access you can try the following command-
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
Those commands are from here http://forum.xda-developers.com/showthread.php?t=2451696 and what they do is they remove the ota so that it's like you didn't take it before and may let you boot into os without having to flash back to stock, but if it doesn't work then your only other choice is flash back to stock
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
kolokoy said:
I have not yet flash the stock rom. Before attempting to experiment on below, have you tried below procedure?
Click to expand...
Click to collapse
I've done a lot of reading on xda over the years so I know some of the do and don't when you have root/custom recovery and don't get in too much trouble with my phones
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Now i cant get an access on adb, what would i do? btw, i using CWM
XxZombiePikachu said:
if you have not already flashed back to stock and have adb access you can try the following command-
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
Wait my friend, don't worry anymore with all this info, just translate the link and OTG flash the small .zip file, piece of cake. Let me know.
http://www.htcmania.com/showthread.php?t=746320
http://forum.xda-developers.com/showthread.php?p=51072849
try this
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs
Is it possuble to local upgrade to 9.0.12 from open beta 4?
Tuneer said:
Is it possuble to local upgrade to 9.0.12 from open beta 4?
Click to expand...
Click to collapse
No, it won't let you.
Caltinpla said:
No, it won't let you.
Click to expand...
Click to collapse
So, then we have to wait for the next stable update for us to go back to stable?
( i know there is a method using msmtool but i am kinda avoiding that)
Tuneer said:
So, then we have to wait for the next stable update for us to go back to stable?
( i know there is a method using msmtool but i am kinda avoiding that)
Click to expand...
Click to collapse
There's uncertain if local upgrade ever worked to switch back to stable from beta! I read from other forums users got soft brick from doing so.
You can use the MSM download tool to switch back to stable then local upgrade will work but it will wipe your phone clean. Or unlock your bootloader then use fastboot to flash the update zip.
Caltinpla said:
There's uncertain if local upgrade ever worked to switch back to stable from beta! I read from other forums users got soft brick from doing so.
You can use the MSM download tool to switch back to stable then local upgrade will work but it will wipe your phone clean. Or unlock your bootloader then use fastboot to flash the update zip.
Click to expand...
Click to collapse
Whoa, didn't know that! Thanks for the info.
Dirty flashing 9.0.12 to Beta 4 and back using TWRP works fine.. I've done it 50 times, literally.
As long as you are bootloader unlocked, TWRP.
Download Full OTA zips.
Flash Zip in each partition, after _b, flash tWRP again, reboot to Recovery
Flash Zip again, it should be in _a after the reboot to recovery.
Flash OTA zip, flash TWRP, reboot recovery.
Flash Magish, kernel..reboot system, 2x times.
Should be rooted with which ever version you are going back/forth between.
Data always intact.
Of course, do at own risk, backup data using the Migrate tool, copy folder off your phone to computer just in case.
Sure, ... you can always flash partitions with "dd" if you have adb installed.
Unzip the original OnePlus zip file, extract the partitions from payload.bin (use python script payload_dumper.py, it's on XDA).
Use a script like this:
Code:
dd if=/sdcard/abl.img of=/dev/block/bootdevice/abl_a
dd if=/sdcard/aop.img of=/dev/block/bootdevice/aop_a
dd if=/sdcard/bluetooth.img of=/dev/block/bootdevice/bluetooth_a
dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/cmnlib64_a
dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/cmnlib_a
dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/devcfg_a
dd if=/sdcard/dsp.img of=/dev/block/bootdevice/dsp_a
dd if=/sdcard/dtbo.img of=/dev/block/bootdevice/dtbo_a
dd if=/sdcard/fw_4j1ed.img of=/dev/block/bootdevice/fw_4j1ed_a
dd if=/sdcard/fw_4u1ea.img of=/dev/block/bootdevice/fw_4u1ea_a
dd if=/sdcard/hyp.img of=/dev/block/bootdevice/hyp_a
dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/keymaster_a
dd if=/sdcard/modem.img of=/dev/block/bootdevice/modem_a
dd if=/sdcard/oem_stanvbk.img of=/dev/block/bootdevice/oem_stanvbk_a
dd if=/sdcard/qupfw.img of=/dev/block/bootdevice/qupfw_a
dd if=/sdcard/storsec.img of=/dev/block/bootdevice/storsec_a
dd if=/sdcard/system.img of=/dev/block/bootdevice/system_a
dd if=/sdcard/tz.img of=/dev/block/bootdevice/tz_a
dd if=/sdcard/vbmeta.img of=/dev/block/bootdevice/vbmeta_a
dd if=/sdcard/vendor.img of=/dev/block/bootdevice/vendor_a
dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/xbl_config_a
dd if=/sdcard/xbl.img of=/dev/block/bootdevice/xbl_a
Reboot in TWRP, push all extracted *.img files to /sdcard/, push above script to /sdcard/doflash.
Then do:
Code:
> adb shell
> source /sdcard/doflash
If you don't know what this all means ... well ..