Related
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Im having the same issue too
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Try this? http://forum.xda-developers.com/showthread.php?t=2451696
I finally solved the issue, miraculously, nothing was working so I just left the phone to continuing formatting for an hour so, came back, and it seemed to have done it, I installed Custom ROM, and it booted up normally, I'm not sure what triggered the phone to accept the system mount, but I am sure as hell happy it did. I was worried I was going to have a bricked device on my hands.
Hold strong, just allow the phone to continue doing what it needs to do I guess. Leave TWRP in all STOCK settings, I tried to modify multiple settings based on Devs saying to get a faster formatting to enable RM-F but I have no clue why and what didn't work.
Anyhow, problem resolved!
On another note, I would never use the recommended method from Droid_<3er as they would completely brick your phone unless you're specifically in the situation listed in that thread. As you would put your phone into a state where you lose both access to Recovery and ROM access, rendering your phone to a piece of plastic and metal. But it's definitely worth mentioning, I just had to do some research on the method cause I had the same thinking as well.
I can confirm by using normal make_ext4fs while formatting /system is the best way to avoid this. Was afraid of having a 5.2 inch brick, but thankfully, disabling the quick way to format has fixed it and allowed /system to be remounted.
I think (<-- that's the disclaimer) that it's OK to use the fast formatting method for Dalvik Cache and Cache, but not for System.
in my opinion it's best to use rm -rf /system aka delete_recursive("/system"); than formatting
I'm having the same issue, and I'd be willing to try this one. How would I do this?
I have the same issue with CWM and now got over to twrp with the same outcome.
Right here I see solutions that worked so far, but it seems like this was rather accidentially.
I want to try some of these, but in the thread posted above
"Try this? http://forum.xda-developers.com/show....php?t=2451696"
it says "Do it the wrong way and your phone might get nuked"
unfortunately it doesn't say what the commands in there mean...
Can anybody be of assistence which method will properly work without nuking the phone?
I have the MOTO G 2014 (2nd Gen)
It is an updated bootloader
i got the latest twrp
and some titan roms.
only stock rom will work so far,
custom roms will result in a bootloop.
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha
Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Updated// 2018-08-24
Cutted file /system/priv-app/Setup-Wizard/setup-wizard.apk to another folder successfully booted ROM, now trying to download another ROM.
After download and reboot in TWRP internal storage shows 0 and cant access to ROM.zip, after change trick data wipes and after boot it show again clear phone. PC still don't see and cant turn on developers options.
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Click to expand...
Click to collapse
Part 1
The fact that you can use Twrp is great news! and its okay the phone is fine as long as TWRP is installed and the bootloader is unlocked. its no big deal not having an OS. As long as you have Twrp you are fine.
You are not bricked.
But, you need to be extremely careful with anything that you do regarding the Elite X722, if you brick it we do not have a qfil file to fix it and you will have no solution.
I do not have a X722, I have the X727 and I generally do not like giving advice on the X722 because of its volatility and there is no option to save bricks.
Here is the main link for the X722, only use roms that are compatible with the X722.
https://forum.xda-developers.com/le...elite-model-x722-guides-development--and-mods
You need to choose a reliable rom, gapps and Magisk.
I would highly recommend AICP
AICP is an excellent rom that works extremely well on the X722,
Everything that you need is with the original post page.
Get AICP here: https://forum.xda-developers.com/le...mods/rom-aicp-13-1-pro3-aka-zl0-x722-t3730711
You already have Twrp installed, follow the steps below for the installation of Rom, Gapps, Magisk
First, you can of course use ADB but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. I recommend at least 32GB. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
If you do not have an OTG adapter and drive
First place your rom, Gapps, and Magisk within storage ( aka: sd card) using your desktop and follow steps below.
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu, by clicking home button.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, clicking checkboxes for TWRP, Reboot to Recovery first, then reboot to system.
Finished!
Edit: Since the PC does not see the phone, additional steps to come in few minutes.
---------- Post added August 24th, 2018 at 12:04 AM ---------- Previous post was August 23rd, 2018 at 11:57 PM ----------
[/COLOR]
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Click to expand...
Click to collapse
Part2 : Stay at ext4, use nothing else, there is virtually no benefit in using F2FS, the speed increase is in the milliseconds.
If these steps below do not work, try another computer or another cable. Or better yet just be patient and get the OTG adapter and USB drive before doing anything else.
[B ]If you can use ADB [/B]
You can save your self alot of time by looking up how to give ADB system wide privileges: this will allow you to flash files without tying the directory path.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your stoarge
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Again , if you do not use an OTG drive. Just use ADB for flashing your files, the steps are same as with any other phone.
---------- Post added at 12:13 AM ---------- Previous post was at 12:04 AM ----------
Post 3,
I just reread your post and only now seeing the partition size issue. The size issue will be resolved after formatting your storage, this is a strange issue, but is fixable. At this point you need to be extremely careful, if you lose you your boot, and recovery you are in trouble. FYI the boot and recovery are on different partitions., formatting storage does not affect them.
Specifically what did you flash?
No doubt, you flashed something not for the X722?
Question
Were you previously using a custom Rom?
Do not try flashing alternate firmwares,
There are several firmwares out there that will brick your phone, Go to you forum that I linked above for the safe versions. @D1stRU3T0R has a X722, perhaps he can chime in here and help provide some further advice on helping you out.
I am thinking that if you can use the All in One tool to flash the X722 stock Rom, you can have a fresh start. @D1stRU3T0R, if you are ssing this mention, care to comment? Thanks
Post 3,
I just reread your post and only now seeing the partition size issue. The size issue will be resolved after formatting your storage, this is a strange issue, but is fixable. At this point you need to be extremely careful, if you lose you your boot, and recovery you are in trouble. FYI the boot and recovery are on different partitions., formatting storage does not affect them.
Specifically what did you flash?
No doubt, you flashed something not for the X722?
Question
Were you previously using a custom Rom?
Do not try flashing alternate firmwares,
There are several firmwares out there that will brick your phone, Go to you forum that I linked above for the safe versions. @D1stRU3T0R has a X722, perhaps he can chime in here and help provide some further advice on helping you out.
I am thinking that if you can use the All in One tool to flash the X722 stock Rom, you can have a fresh start. @D1stRU3T0R, if you are ssing this mention, care to comment? Thanks
Click to expand...
Click to collapse
I think my last hope is otg, or usb drive to android phone because after many tries still can't connect phone to pc no new devices in device manager, phone only charging, tried now with 3 different pc and 3 different cables. Tried to install this ROM: https://forum.xda-developers.com/le-pro3/development/rom-dotos-2-3-1-t3809068 last ROM was paranoid and working well, but I have bored and wanted 8.1 Android, so..
kiamikadze said:
Hello,
I have leeco le pro 3 x722 and problem happened that I have tried to flash to another ROM from AOSP to DOT, so I have made backup and tried to flash after wipe I realised I have wiped everything and now don't have any ROM inside phone, I have connected phone to pc but it does not show in device manager and nothing happens it only charges. I have TWRP recovery and I can only explore in it. Did I bricked my phone already? How can I recover it? did TWRP wipes backups too ? Also in TWRP it shows Internal Storage (0 MB seems wiped) and U(USB Storage)(0MB). Tried to connect with differend cables - same situation still no reaction only charging. On Backup Tab it shows that I have System Image 4gb, System 1,4gb, Boot 64mb
Updated//
Fixed partition now it shows internal size.
1.Changed data partition from ext4 -> fat > and change it again to same it succesfully recovered but after reboot it gone again.
2.Tried on diferent pc to connect phone - still no MTP.
Updated// 2018-08-24
Cutted file /system/priv-app/Setup-Wizard/setup-wizard.apk to another folder successfully booted ROM, now trying to download another ROM.
After download and reboot in TWRP internal storage shows 0 and cant access to ROM.zip, after change trick data wipes and after boot it show again clear phone. PC still don't see and cant turn on developers options.
Click to expand...
Click to collapse
@tsongming thanks.
So, first of all, you try to say that you made a backup but you wiped everything so now our phone is empty, and you can't connect it to PC nor use sdcard(logic) and OTG doesn't see your USB?
So, listen here, i had this problem too xd.
First, what format is your usb stick? If I remember well, NTFS is working (assuming you have pretty nes TWRP). Try to format the stick to NTFS, or try with another one. Your only option now is to find a compatible USB stick and to make it work with OTG, than you csn flash any rom you want.
When you get the USB working, install newest twrp, 0.3.2.1-3 or smth like this, than Genesys 26S, as a base stock rom, than AICP and blackscreen OC kernel, or whatever rom you want.
My wife has a 722 too. Mtp is never working on my PC. So i habe to usw ADB for file transfer. Just type "adb devices" if there is shown your device its working (must be in twrp at least and connectet via cable) then just type "ADB push " path to file" /sdcard" and it will copy the file to the phone.
I would first update twrp then modem.ZIP for x722 and then Rom gapps and magisk if u want.
oiseau1201 said:
My wife has a 722 too. Mtp is never working on my PC. So i habe to usw ADB for file transfer. Just type "adb devices" if there is shown your device its working (must be in twrp at least and connectet via cable) then just type "ADB push " path to file" /sdcard" and it will copy the file to the phone.
I would first update twrp then modem.ZIP for x722 and then Rom gapps and magisk if u want.
Click to expand...
Click to collapse
As @D1stRU3T0R mentioned you will not need the PC once you have the PTG adapter and the USB 3.0 drive.
Make sure its USB 3.0 otherwise it may take a while before your phone will recognise the flash drive. I bought my OTG adapter and a 32GB usb 3.0 flash drive for $14 at Walmart for both!
tsongming said:
As @D1stRU3T0R mentioned you will not need the PC once you have the PTG adapter and the USB 3.0 drive.
Make sure its USB 3.0 otherwise it may take a while before your phone will recognise the flash drive. I bought my OTG adapter and a 32GB usb 3.0 flash drive for $14 at Walmart for both!
Click to expand...
Click to collapse
I have 2 usb 2.0 and they both work (with some cheap old otg cable), so OP can try whatever stick he wants.
And i guess you mean OTG not PTG
D1stRU3T0R said:
I have 2 usb 2.0 and they both work (with some cheap old otg cable), so OP can try whatever stick he wants.
And i guess you mean OTG not PTG
Click to expand...
Click to collapse
Ha, Ha. Yes OTG, its my stupid autocorrect, on this awesome chroma keyboard. Keyboard is great, with its amoled theme, the autocorrect, not so good.
Yes, I used to use large 2.0 drives too. But, once they become about 80 percent full, I would need to wait 20-30 seconds, sometimes longer for them to show up in recovery. To make matters worse, sometimes I would need to reboot to recovery for them to appear at all. On the the other hand the much, much better USB 3.0 reliably always show ups and instantly.
To go on, the transfer rate difference plays a significant factor when creating or restoring a large full nandroid backup. For example, The transfer rate of USB 2.0 is a mere 60 Mbps while transfer rate of USB 3.0 is 640Mbps. Yes, this speed difference is in fact a huge time factor when restoring a 11GB full recovery!
Respectfully use whatever you want, but I am not going to ever recommend anything less than USB 3.0 Its funny, for a person whose always wanting the maximum overclocking speed, and absolute full use of the battery. I am frankly very surprised you would use anything less than USB 3.0..... Lol. its okay, just winding you up, I guess that I have much less patience than you. Ha ha
FYI, USB 3.0 drives are nearly the same price as the USB 2.0 drives.
I paid $2.00 for my OTG adapter and $11 dollars for by USB 3.0 drive. Better yet, I went back a week later and Walmart had a package with two USB 3.0 drives on sale for only $20!
Sent from my LEX727 using XDA Labs
first of all what version is your twrp,because newer roms need newer twrp
i did the same mistake on my x722 and managed to install new rom using adb sideload from twrp,pc and a data cable,just look into it how to install rom from pc using adb sideload or if the otg arrived is easyer to install from a flash drive with otg
So, first of all, you try to say that you made a backup but you wiped everything so now our phone is empty, and you can't connect it to PC nor use sdcard(logic) and OTG doesn't see your USB?
So, listen here, i had this problem too xd.
First, what format is your usb stick? If I remember well, NTFS is working (assuming you have pretty nes TWRP). Try to format the stick to NTFS, or try with another one. Your only option now is to find a compatible USB stick and to make it work with OTG, than you csn flash any rom you want.
When you get the USB working, install newest twrp, 0.3.2.1-3 or smth like this, than Genesys 26S, as a base stock rom, than AICP and blackscreen OC kernel, or whatever rom you want.
Click to expand...
Click to collapse
After many tries it didn't help I have tried with NTFS, FAT32 still same didn't recognized otg storage, uploaded ROM to flashdrive when in TWRP checked storage of usb drive, cant even choose mount usb drive, or just take data from usb in Leeco. I don't know what to do I think I should recycle it ..
I have installed many ROMS and unbricked many phones but this one is "Die Hard" don't know what to do more when cant connect via usb/otg. Many thanks for help, I think for now is impossible to reflash any rom, still not wiped system data so I can boot my phone without setup wizard and he runs.