Related
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Jeff5886 said:
Ok I had my phone rooted and had voodoo on it. The phone was having issues downloading from the market, plus I couldnt turn the phone on unless i had it pluged in. So I tried to reset it using odin and the Stock-i500-VZW-Recovery.tar.md5. Now when I turn the phone on i get the android application has an uxpected error and I cant get past that. What do I do? Or how can I get my phone back to stock so I can re-root it.
Click to expand...
Click to collapse
Jeff,
See this post for returning to stock http://forum.xda-developers.com/showthread.php?t=782204. I would do this as a last resort only.
Good Luck!
that is what got me to this problem. there are multiple files there what one do i use?
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
I was having the same issues with USB cable looking like it was plugged in so I couldn't reboot unless it was plugged. I tried the voodoo uninstall and screwed up my data partition.
I ended up restoring the CWM_Kernel and Di01 Stock update which brought me back to stock with root and OTA update from Verizon BUT my Data partition is screwed and I have no internal app memory. Also, I have an Nandroid backup that I tried to install but that causes the FC issues that you mentioned. My guess is that my nandroid backup will work once I fix the data partition.
Later tonight, I'm going to try to put the stock MBR back onto the phone which I think you need to do as well.
However, it sounds like you didn't complete the whole recovery process and only applied one file. I'm an android newby so you can't take my advice to the bank but I think you need to restore all the files if you're going to flash with Odin per those instructions.
For me, I had CWM loaded so I just wiped the kernel and put back the DI01 ROM which put me back to stock albeit with some work to do to get my data partition back in shape. I hope this helped, for what it's worth.
Since you've already got the original.mbr copied and the stock.zip flashed...
Boot into CWM recovery and wide data/cache.
If you have a CWM backup of your phone in a rooted state, restore that backup through CWM.
Reboot, and go into "settings" if possible at this point, and factory reset.
This got me back from market failure/0.00/fc hell after utterly failing to heed the voodoo warnings and trying to revert to stock without undoing the lagfix.
You'll likely need to use the unsigned d101 apk if your backup/flash is dh12. The OTA update did not work for me at that point.
phispher said:
You apply them in the order they are listed.
1. Apply the "/system" file first
2. Apply the "kernel" file second
3. Apply thie "recovery" file third
This restores stock /system, the stock kernel, and the stock recovery. Pretty much brings you back to stock. Is that what you're trying to do?
Click to expand...
Click to collapse
My question is do i use the phone. pda or csc buttons for these files?
Ok in Odin use the PDA button for the /system
but what button do i use in odden to load the kernal.tar and recovery.tar
i loaded the pit, and installed all the files using the pda button one after the other. now my phone get no service and it still isnt wiped. what is going on? how do i get the phone back to out of the box condition.
also, now i cant do a factory wipe/reset, im getting the error message Can't mount /dev/block/mmcblk0p1
Gotta do the mbr fix from the 0.00 internal memory topic and then restore nandroid recovery.
Oh, and it is PDA for all three files, not just system.
Sent from my SCH-I500 using XDA App
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
trapstarr56 said:
i have the same problem n i havent had a phone for a
week...whats the fix??? did u fix urs??
Click to expand...
Click to collapse
Use the uninstaller form Here:
http://forum.xda-developers.com/showthread.php?t=804784
If that does not solve it, follow the steps here:
http://forum.xda-developers.com/showthread.php?t=782204
Read all pages of each topic completely prior to initiating *either* of them.
as captioned, whats the advantage of doing so?
what are updated by the stock rom that are not updated by the cutomised rom?
recovery.img? i have manually replaced with CWM one..
amss.mbn? i have also manually replaced with the B162 version..
what else then?
now im with oxygen rom (was with B136 stock rom), say if there are indeed certain files from the latest stock rom that i should have, what is the best way to get them updated?
Have a look at this.
XphX said:
Have a look at this.
Click to expand...
Click to collapse
yeah thx.. i read that topic previously..
what im expecting is a bit more technical, such as what actually are being covered by stock rom while not touched by custom roms, where those files in "dev', "etc", "sbin", "sys" come from (since seemingly they are not included in oxygen rom when i check the zip file content), etc..
if these files are from the stock rom im using before flashing a custom rom (oxygen + B136 in my case), then im not just experiencing oxygen, rather a mixed experience of oxygen & B136..
if this is the case, the problems/issues i encountered might not be solely related to oxygen and might actually related to the stock rom..
anyway im very new on linux and smartphone stuff.. any information to enlighten would be much appreciated..
It won't be a mix of two ROMs at the same time, if you install your custom ROM with that instruction:
In Recovery menu: Choose Wipe Data /Factory Reset, then go back to main menu. Choose Wipe Cache Partition, then go back to main menu. Go to Advanced and choose Wipe Dalvik Cache, then go back to main menu. Then install the ROM by using the zip-file you placed on the sd-card earlier. That will delete what's left of the previous ROM. If you don't do this, you will run into problems eventually. But if you just wipe everything before flashing the old ROM cannot interfere.
Do not extract the zip-file of a custom ROM, just install it as it is.
iamelton said:
what actually are being covered by stock rom while not touched by custom roms
Click to expand...
Click to collapse
Updates for baseband, maybe also for other components.
iamelton said:
where those files in "dev', "etc", "sbin", "sys" come from (since seemingly they are not included in oxygen rom when i check the zip file content), etc..
Click to expand...
Click to collapse
Well Android does some stuff at the first boot and it does install some files (I do not know what it does exactly). If you followed the instructions these files cannot be from another ROM.
What other questions do you have? You just wrote "etc.", I cannot know what you want to ask...
u already helped a lot.. thx.. 8)
[edit]
oh just one more question, whats an "update to baseband" then?
amss.mbn? or can i even find it in the form of a file in root explorer?
I don't think that all the data gets replaced even when wiping both caches and doing a factory reset before applying new ROM. I just did that yesterday with new MIUI release, but I can still find data from my very first stock-ROM! In cust_backup/image/cust_data is folder called elisa(finish network provider, from which I originally bought the phone) with all the bloatware(gameloft installerinstallers for example), finish swype and more (folders are: app, lib, logo, prop, wallpaper, xml). Yesterday, I deleted it (the whole "elisa" folder with Root explorer (since I thought that: I have this new ROM, I don't need this old remnant crap of froyo). Well, as it turned out, I DO NEED this old crap, since after reboot phone just froze after operator logo( I honestly don't know how the logo was even possible, since it was in the folder I deleted). Had to restore from recovery and now it is back again..
Q: if I update to latest official rom, will the data in cust_backup be updated? Is this the point of applying latest stock-release once in a while?
Sent from my u8800 using xda premium
Vk_ said:
In cust_backup/image/cust_data is folder called elisa(finish network provider, from which I originally bought the phone) with all the bloatware(gameloft installerinstallers for example), finish swype and more (folders are: app, lib, logo, prop, wallpaper, xml).
Click to expand...
Click to collapse
I have the same folders, but for Estonia Elisa. I don't understand why is it there, when I have a totally different ROM.
Sent from my Huawei u8800 using XDA App
Well that is not surprising Vk_, I have all those apps and stuff too and if you delete the wrong file there, well... good thing that you cannot brick your phone
The partition mounted to cust_backup won't be overwritten by the wiping that is usually done before installing a new ROM. This is because it contains the files needed for entering recovery-mode etc.
This Elisa-folder contains stuff that is needed, maybe even the bootlogo (I just thought about this for a few minutes now, so I don't know what it is for). This has nothing to do with the ROM previously installed or with the Huawei-ROM. This folder is necessary for every u8800-device to work properly regardless of which Android-ROM is installed. Mine is called 2020 instead (that might depend on where you got it from).
Vk_ said:
if I update to latest official rom, will the data in cust_backup be updated? Is this the point of applying latest stock-release once in a while?
Click to expand...
Click to collapse
The point of applying the newest release is that you can make sure to get the latest baseband-firmware and maybe even updates for other parts. I do not know if these updates are installed via cust_backup but that could just be the case. It isn't important though; at least I get great reception everywhere so I do not need to update the baseband.
iamelton said:
oh just one more question, whats an "update to baseband" then?
amss.mbn? or can i even find it in the form of a file in root explorer?
Click to expand...
Click to collapse
The baseband updates the program that controls the radio-chip. This firmware has its own area on the radio-chip, this firmware won't be stored on the device. But a file to update this firmware will be on the device (maybe it is deleted automatically after updating).
now i think im much clearer.. thx..
then probably i dont need to update to B138 as i have good signal reception everywhere, and can sleep well since i know my phone is not with sub-perfect firmware.. 8)
for the cust-backup discussion, i also had similar doubt before..
glad that i didnt really go ahead to remove this useless "/cust_backup/image/cust_data/pccw/hk/" folder tree..
i just wonder how it manage to survive between rom wipes and installs..
this pccw folder came from the provider where i bought my phone, and in B136 rom its "/cust_backup/image/cust_data/hw/ideos_x5/"
after flashing B136, my phone could boot but things like custom boot animation, ring tones were lost..
i had to rename "hw" to "pccw", "ideos_x5" to "hk" to make them re-appear..
thus the linkage to this special folder tree seems to survive after complete wipes..
anyway before anyone tells me how to remove the whole tree, i shall leave them there..
Yes I wrote that this partition never gets wiped or anything, so that is why it survives every wipe and ROM-install.
XphX said:
Yes I wrote that this partition never gets wiped or anything, so that is why it survives every wipe and ROM-install.
Click to expand...
Click to collapse
actually it gets wiped (probably by the update_cust.app part in the B136 stock rom)..
before its "/cust_backup/image/cust_data/pccw/hk/"..
and after flashing B136 it changes to "/cust_backup/image/cust_data/hw/ideos_x5/"..
thus its updated, but somehow i have to manually rename "/hw/ideos_x5/" back to "/pccw/hk/" in order to make my custom boot animation and ring tones work again..
they were put in "media" folder under the tree, but somehow they wont work until i change the folder names back to "/pccw/hk/"..
thats why i said the "linkage" to these folder tree got survived between rom installs, but not the folder tree itself (which was updated by update_cust.app)..
No it does not get wiped. The stock ROM (and for that matter, every ROM can do that) simply changed the files in the directory you specified in your post. It does not matter anyway (so why am I writing this?;D).
XphX said:
No it does not get wiped. The stock ROM (and for that matter, every ROM can do that) simply changed the files in the directory you specified in your post. It does not matter anyway (so why am I writing this?;D).
Click to expand...
Click to collapse
just for the sake of discussion, maybe?!
Alrighty, I made two threads about this before and for some unknown reason they have been deleted? Either way, i'm going to ask a simple basic question then and not get into details this time.
How do I completely and utterly wipe everything on my phone so I can start over from scratch like it is brand new?
I've gone into CWM and the format section and have done every option there minus firmware. Not entirely sure how i'm gonna get access to my SD car now to toss on my ROMs an such again but desperate measures indeed going on here.
If I format the firmware as well what will it do?
There's files hidden on my system that I need to get rid of. I'm sick and tired of this app restoring old data when i've spoofed and changed all of my info. There's no possible way it should be able to which means it's hiding stuff somewhere in my folders deeply tucked away. Solution? I will delete and format EVERYTHING.
Help?
Flash the factory images.
I'll have to look up how thanks.
I formatted everything in a rage fit and wiped the SD card before flashing a new ROM so i'm sort of stuck in recovery right now and I don't know how to access it to put more files on via USB.
ZackBanditMan said:
I'll have to look up how thanks.
I formatted everything in a rage fit and wiped the SD card before flashing a new ROM so i'm sort of stuck in recovery right now and I don't know how to access it to put more files on via USB.
Click to expand...
Click to collapse
I edited my post with a link to the instructions.
This will completely return your phone back to how it was when you first got it.
Chromium_ said:
I edited my post with a link to the instructions.
This will completely return your phone back to how it was when you first got it.
Click to expand...
Click to collapse
Read through it now and got the files in a directory, phone in bootloader but when I open the command prompt it doesn't allow me to type the commands. Is this because I formatted everything on the phone and it's not recognizing as a device?
I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
My repository is here: https://github.com/zyrill/android_device_lenovo_b8080h
And the CWM recovery image is attached. Use towelroot by geohot to root your tablet.
Before attempting to flash, you should:
make sure you know what you're doing!
double check that you're flashing the right partition!
If you flash the wrong partition, you'll brick your tablet!
You can check your partition layout with
Code:
$ ls -al /dev/block/platform/msm_sdcc.1/by-name/
Once rooted, you can flash the image as follows:
Code:
$ adb push recovery.img /storage/sdcard0/recovery.img
$ adb shell
$ dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p21
Enjoy!
Changelog:
v 0.1: Initial version. Known issue: can't yet mount /sdcard and external cards
v 0.2: Backup is operative! Known issues: no option to backup to external storage, no option to skip backing up of external storage, date is not set correctly
zyrill said:
I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
Click to expand...
Click to collapse
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
asmaron said:
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
Click to expand...
Click to collapse
Yep! I´ve done! TowelRoot works.
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root! But don´t forget to install SuperSu!
Bringer1 said:
Yep! I´ve done!
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root!
Click to expand...
Click to collapse
Thanks! I'll give it a try later on!
asmaron said:
Thanks! I'll give it a try later on!
Click to expand...
Click to collapse
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Most Excellent
zyrill said:
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Click to expand...
Click to collapse
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Oh Yeah
Oh yeah, I forgot to mention that I've got the WiFi only version. That's the 8080-f hardware version. The recovery block is the same.
B5Pilot said:
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Click to expand...
Click to collapse
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
tdklaus said:
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
Click to expand...
Click to collapse
I may have a little premature in my enthusiasm. My backup included a full copy of my SD card which nearly filled the remaining internal memory. I never did try to restore the backup so I can't guarantee that it would work correctly.
I've started the process of compiling a version of CWM for the WiFi only version but I'm new to the whole process and it will take me a while to begin to figure it out.
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know.
Mark
B5Pilot said:
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know. Mark
Click to expand...
Click to collapse
I have captured the OTA to 4.4, so if you tell me how, I could try to extract the original recovery from it.
CM 11 would be great
Thanks for your attention to our HD+ tablets. I have B8080-F. Lenovo seems to be pretty slow in bringing new Android versions to this new tablet. It would be great to have CM 11 builds for this device. I have a Samsung Tab 2 7.0 that got new life after I installed CM 11 4.4.4..Just my encouragement to you folks who know how to build CM for the HD+.
Edit:
4.4.2 firmware have WiFi problems,problems with some apps like weather and so on. I went back to 4.3
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Regarding CWM: I've just finished my PhD and am looking for a job. As soon as that's settled, I'll have time to work on other projects such as CM for our tablet. But in the meantime, if anybody makes any headway, simply issue a pull request and I'll include your work in our repository so everybody can benefit.
Cheers!
zyrill said:
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
thx, zyrill.
Well what cam I say, booted into recovery, chose backup/restore - backup and after a few messages the process seemingly stopped with "backing up /sd-ext" on the screen.
No ext-partition existed on the external sdcard, and there were about 10GB free on the internal and 27GB on the external, so wherever CMW tries to store it's files, I hope there was ample room.
I'd still very much appreciate the original recovery.img before I do any more experiments (it's the wife's tablet, after all
zyrill said:
Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
tdklaus said:
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
Click to expand...
Click to collapse
Sure, I'll upload the files once I get back to Germany next Tuesday. Am away and without access to something else than Android... I'll get right on it once I'm back.
Alright, excuse my belated reply. But here we go: I have uploaded the original recovery.img - see the attachment.
I have rooted through towelroot, haven't touched the recovery. I got the "b8080_s101103_140715_row_wifi" update but it failed to apply because of the LenovoSafeCenter.apk being altered.
Any way to update ?
Edit : I tried to restore the factory settings. The update still won't install.
DannyBiker said:
(...)because of the LenovoSafeCenter.apk being altered.
Click to expand...
Click to collapse
I don't think this has anything to do with towelroot as it doesn't alter any of your apk's. But anyway, for your convenience, here's an unaltered version of that file (see att.). Cheers!
Cool thanks ! I'll try that tonight...
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
crazyc78 said:
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
Click to expand...
Click to collapse
I saw your other post in the other thread, but couldn't reply for some reason.. did you wipe the internal storage before restore?
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
crazyc78 said:
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
Click to expand...
Click to collapse
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
ricosuave88 said:
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
Click to expand...
Click to collapse
I used the deodexed ROM that is in the development forum. If I can upload it here I will if not just download it put it on your SD card and flash it. It may take a couple tries though I would suggest powering down your phone instead of rebooting it. Then turn it on and it should boot into the new rom. It's basically the same stock rom that our phone comes with. You may have to flash Chainfires SUPERSU zip that's in one of the threads. These steps should get you up and running again. Also if you can see your internal storage you're not encrypted. Hopefully that works for you. Let me know how it goes.
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
crazyc78 said:
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
Click to expand...
Click to collapse
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
ricosuave88 said:
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
Click to expand...
Click to collapse
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
crazyc78 said:
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
Click to expand...
Click to collapse
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
ricosuave88 said:
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
Click to expand...
Click to collapse
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
crazyc78 said:
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
Click to expand...
Click to collapse
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
kaiser10 said:
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
Click to expand...
Click to collapse
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
crazyc78 said:
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
Click to expand...
Click to collapse
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
kaiser10 said:
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
Click to expand...
Click to collapse
Np don't give up, I almost lost hope and then it worked for me.
Like I said there was another method that was discussed that worked for someone else. Try this thread, I know someone had the same issue that you and I had and they finally got it working.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
I'm here to the rescue! Follow this to the T! It worked for me! Let me know. http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
im on the same boat as you. I am stuck in TWRP
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
hslayer said:
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
Click to expand...
Click to collapse
Same. Though I am on US996. Not sure what I did, was exploring some behind the scenes stuff using 'hidden codes' but didn't change any values as I didn't know what they meant in most cases. I rebooted my phone and it went straight to TWRP (3.0.2-1) and it will not boot past TWRP. Occasionally after I've flashed something, it will boot into TWRP and the screen will be unresponsive to touch so I have to pull the battery, but then it will be fine again.
I was in your position not to long ago, I'm currently working on getting a .kdz recovery file for the H918. My progress will continue on it later when finals are over.
netgar post 134
Restore H918 to 100% Stock (!!REQUIRES TWRP!!)