Related
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250
hi guys
I tried to install a custom rom on my HTC One X PLUS. I am new to this and it looks like i kinda screwed up. i used "HTC One X+ AIO Kit By Hasoon2000 v2.3". I have now this "CWM-based Recovery v6.0.2.7" on my phone. i can't boot the normal OS anymore. everytime i reboot, this cwm recovery shows up. when i try to install cyanogenmod (cm-11-20140705-NIGHTLY-enrc2b.zip) by "install zip from sdcard => choose zip from sdcard ==> ..." i just receive:
Code:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/cm-11-20140705-NIGHTLY-enrc2b.zip
(Status 7)
Installation aborted.
i have no idea what to do. can anyone pls help? is it still possible to reset everything to get my phone working again?
Flash the latest version, older ones can't flash kitkat ROMs
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-enrc2b.img
Sent from my One X+ using Tapatalk
Phoenix09 said:
Flash the latest version, older ones can't flash kitkat ROMs
Click to expand...
Click to collapse
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Hutschi93 said:
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Click to expand...
Click to collapse
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
leefear said:
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
Click to expand...
Click to collapse
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Hutschi93 said:
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Click to expand...
Click to collapse
did you flash the recovery that phoenix suggested?
leefear said:
did you flash the recovery that phoenix suggested?
Click to expand...
Click to collapse
how? i just can open this cwm based recovery mode or this strangely HBOOT mode. but my computer doesn't really recognize it. if i open the device manager i see it under "ADB Interface" as "HTC Bootloader" but if use "adb devices" in command prompt my phone does not get recognized. the toolkit doesn't recongize it either.
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Hutschi93 said:
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Click to expand...
Click to collapse
glad u got it working bud!
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
ezugaru said:
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
Click to expand...
Click to collapse
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
Hi, this is what i used to downgrade : http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Hope it helps, i'm at the office now, so when i get home I'll check where i got the resources to downgrade since i used my personal computer to do it.
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
ezugaru said:
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
Click to expand...
Click to collapse
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
gypsydanger said:
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
Click to expand...
Click to collapse
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
ezugaru said:
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
Click to expand...
Click to collapse
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
gypsydanger said:
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
Click to expand...
Click to collapse
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
ezugaru said:
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
Click to expand...
Click to collapse
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
gypsydanger said:
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
Click to expand...
Click to collapse
Did you give terminal root permissions by issuing the SU command and then granting the permissions on the phone?
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
gypsydanger said:
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
Click to expand...
Click to collapse
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
roirraW "edor" ehT said:
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
Click to expand...
Click to collapse
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
gypsydanger said:
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
Click to expand...
Click to collapse
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
bweN diorD said:
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
Click to expand...
Click to collapse
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
is there a specific version of twrp I need for that nightly?
gypsydanger said:
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
I'm attempting to wipe recovery again and try CWM to see if that will work.
Click to expand...
Click to collapse
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
bweN diorD said:
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
Click to expand...
Click to collapse
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
gypsydanger said:
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
Click to expand...
Click to collapse
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
gypsydanger said:
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
Click to expand...
Click to collapse
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
roirraW "edor" ehT said:
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
Click to expand...
Click to collapse
it says update failed due to an error and you have to hit retry or it does nothing...unless I need to just do nothing.
edit: IT WORKS YAY...all I did was retry and retry (definition of insanity) and the /sdcard just appeared then the dd command worked and I'm in recovery now yayayayayay
edit: edit: I did take out my eternal SD card so I am going to guess and say that that was the problem from the get go...anybody have any thoughts on that??
Managed to download and flash the B130 update on my stf-L09C432. After a factory reset and a couple of reboots it seemed to work fine. It goes through the configuration as supposed all the way to completing configuration. Then it stays there for a minute and then the configuration guide restart. Tried rebooting and wipeing, but it won't go any further.
The settings are saved though and everything is pre-set when I go through the configuration again.
Can it be some kind of permission problem?
Can I bypass the configuration?
I guess there's a flag somewhere for configuration_done = true or something.
Any ideas?
Still doesn't work. Have tried to download several times. Have tried both dload (fails) and flashing with fastboot.
Flashing boot, recovery and system works fine. But it won't permit flashing the vendor partition.
"Command: Not allowed" even if I tried several downloads.
Maybe if someone have a working twrp backup to share with me. Either B130 or B120.?
That might open up so I can flash everything new
Have you tried manually reinstalling the OS back onto your device?
iceepyon said:
Have you tried manually reinstalling the OS back onto your device?
Click to expand...
Click to collapse
Manually like flashing each image separately or is there any other way?
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
Oh. Of course by pushing with adb ?
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
Just reinstall the stock OS back onto your device and see if that helps.
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
iceepyon said:
Just reinstall the stock OS back onto your device and see if that helps.
Click to expand...
Click to collapse
Since I was stupid enough not to make a backup I downloaded the latest stock update.zip and extracted the images from there.
I manage to flash system and boot but not the vendor image. Get "command not allowed".
The partition seem to be ok though, since I can push files to it and according to the simg tools there is nothing wrong with the image.
Is there like a full ROM that I can just install with twrp? I couldn't find any.
Rommco05 said:
Try flash custom.img, I think is in small region zip
Click to expand...
Click to collapse
Ok. Tried a bunch of solutions:
- Install stock full update.zip
with twrp - gives updater error: 9with fastboot - can flash system, boot, recovery but not vendor image.dload folder - stops with failureby unpacking images and using adb puschNone of these works fully and there is always some error, hanging loading screen or boot loop or as from the beginning setup wizzard won't complete.
Question: Which images from the update.zip are actually required on a wiped system? Should I get all of the on to the phone?
Would a fully working twrp backup from a kind soul be a safer way to go?
Also tried the custom ROMs but was unable to flash their vendor.zip files because of wrong header format
and simg2img was unable to read them.
Tried the ROMs with stock vendor.zip but got some java error in main (used logcat)
Been working on this for a week now. at one part I feel like throwing my new phone in the wall, but at another part I kind of enjoy this mess and of course I learn a lot in the process
Where should I go from this?
I would like to get the stock firmware working first so I can take a backup.
zybitx said:
Ok. Tried a bunch of solutions:
- Install stock full update.zip
with twrp - gives updater error: 9with fastboot - can flash system, boot, recovery but not vendor image.dload folder - stops with failureby unpacking images and using adb puschNone of these works fully and there is always some error, hanging loading screen or boot loop or as from the beginning setup wizzard won't complete.
Question: Which images from the update.zip are actually required on a wiped system? Should I get all of the on to the phone?
Would a fully working twrp backup from a kind soul be a safer way to go?
Also tried the custom ROMs but was unable to flash their vendor.zip files because of wrong header format
and simg2img was unable to read them.
Tried the ROMs with stock vendor.zip but got some java error in main (used logcat)
Been working on this for a week now. at one part I feel like throwing my new phone in the wall, but at another part I kind of enjoy this mess and of course I learn a lot in the process
Where should I go from this?
I would like to get the stock firmware working first so I can take a backup.
Click to expand...
Click to collapse
the same problem, i hope we could solve it soon.