Database Info

[Q] HELP!!!!!!!

Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.

donlloreda said:
Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.
Click to expand...
Click to collapse
Get a sdcard reader, stick it to your computer, copy a ROM zip that includes the right kernel for your sdcard (CM7 or any other that includes a kernel), put it back into your phone, reboot into recovery, install zip, wipe data/cache and dalvik cache then reboot and see if it works.
edit:
you can only acess STOCK recovery, then maybe you can try flashing the bootmenu first (http://forum.xda-developers.com/showthread.php?t=1196590&highlight=bootmenu) by copying to your sdcard too with a sdcard reader, flash it from stock recovery, reboot and see if the blue led blinks, if yes then press volume up/down, enter clockworkmod recovery and do the steps above.
if it does not work then im out of ideas.

donlloreda said:
Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.
Click to expand...
Click to collapse
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.

Darin_Ram said:
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.
Click to expand...
Click to collapse
afaik milestone 2's stock recovery can't flash kernel or an entire custom ROM, you need clockworkmod 3 (provided by the custom bootmenu) or above for that purpose.

Darin_Ram said:
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.
Click to expand...
Click to collapse
Stock recovery can`t flash custom zip files.
Gustavo_s said:
afaik milestone 2's stock recovery can't flash kernel or an entire custom ROM, you need clockworkmod 3 (provided by the custom bootmenu) or above for that purpose.
Click to expand...
Click to collapse
I think, that stock recovery can flash kernel and / or entire rom, as OTA updates are made, but zip must be signed with motorola private key ..

ZyrByt said:
Stock recovery can`t flash custom zip files.
I think, that stock recovery can flash kernel and / or entire rom, as OTA updates are made, but zip must be signed with motorola private key ..
Click to expand...
Click to collapse
yea, i think that he needs the bootmenu in order to flash a custom rom (cm9, cm7 or whatever), or like you said a signed update from motorola, but i dont think we can find one.
anyways, im afraid that even flashing the bootmenu he will not able to get into it.

The plug is standard plug. You can buy it in any electronic schop. Any mobile phone service can replace it. It's simple and fast. Only 5 pins to soldier.

I said rename it!
I said to download a kernel, rename it to update.zip and flash it! I'll also upload a picture of my stock recovery so you can see what to select.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello everybody, I have similar problem.
My Mile2 is bootlopping the Motorola logo, I tried flashing various stock roms by RSD lite without result. Also not to get into the stock recovery by pressing X and @. Is there any other way to go back to work?
Sorry my poor english..

Do you can get into recovery with ! symbol? in android 2.3 you must prec vol - and vol + at the same time to get in there. You can also try flas newest sbf. If you flash 2.3 before now you can't flash 2.2. (maby this is your problem)

[SOLVED]Stuck on JB samsung logo and CWM logo

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been running the deodexed UCMC1 with stock kernel until i got my replacement batteries today.
Turns out they had a different model # (EB585157VK, SERIAL AAaD702QS/5-B 2013.07.02) and were slightly thinner then the stock battery (the seller had a skyrocket one pictured on ebay).
Anyway they seem like legit OEM.
I get all stupid and exited to have new batteries and instead of powering off the phone from the menu i just pull out the stock battery and insert the new one. :highfive: (cynical mental highfive)
Phone is now stuck at above samsung logo and cwm only goes as far as the logo and version number, no menu no nothing.
I've read about the same problem someone had with an S3 mini here.
Will odin help me?

Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682

jd1639 said:
Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682
Click to expand...
Click to collapse
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..

lingowistico said:
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..
Click to expand...
Click to collapse
Mohan had a zip that restored the pre-load partition. You might give that a try.

all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom

jd1639 said:
Mohan had a zip that restored the pre-load partition. You might give that a try.
Click to expand...
Click to collapse
Thanks i will. Do you know if it's possible to swap the internal sd for another one?

vincom said:
all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom
Click to expand...
Click to collapse
Old battery didn't help.. After odin I didn't wipe b4 boot :silly:
I'll try TWRP too.

lingowistico said:
Thanks i will. Do you know if it's possible to swap the internal sd for another one?
Click to expand...
Click to collapse
Afaik, the internal is soldered on.

jd1639 said:
Afaik, the internal is soldered on.
Click to expand...
Click to collapse
It's fine though, old CWM 5xxx shows install zip from SD and install zip from internal SD and it's the opposite in new CWM. So it turns out SD is fine, phew Problem is i think it looks for backups only on external so i can't access my backup.
mohans preload fixer didn't help.
I'll try TWRP now.

Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone

Good to hear you got it working again

lingowistico said:
Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone
Click to expand...
Click to collapse
when flashing stock and having boot up problems and such, resetting and wiping the caches with stock recovery usually solves it 99% of the time

Bricked Moto G XT1032?

My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.

You only tried do flash system? Haven't you flashed anything before system?

kirmr said:
You only tried do flash system? Haven't you flashed anything before system?
Click to expand...
Click to collapse
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.

_Drifter_ said:
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.
Click to expand...
Click to collapse
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf

_Drifter_ said:
My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.
Click to expand...
Click to collapse
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.

kirmr said:
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf
Click to expand...
Click to collapse
Unfortunately didn't work. But thanks for the help.
tatazeuz said:
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.
Click to expand...
Click to collapse
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?

Well, good luck mate
I'm sure you'll that fixed very soon.
If flashing original file through adb won't do the trick..
Can't do anything more to help u. Propz.

_Drifter_ said:
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?
Click to expand...
Click to collapse
I made a method to recover your phone for use! Sadly, you will only be able to use custom ROMs (at least until there's a 4.4.4 image)
Check it in my thread
http://forum.xda-developers.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946

Fail to Boot after after Google Play system update (Boot reason : init_user0_failed)

Hello all,
I wanted to report something that happened to me yesterday:
I recieved the following notification:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I selected "RESTART NOW" and when the phone tried to restart, it failed to boot (it didnt even reach the boot animation) and went into recovery. Within recovery there was an option (I think it was called Boot reason) to show the error that prevented the phone to boot into the OS. This was the error:
I tried to pull the files but I couldn't get adb access within the 8T stock recovery. I tried to reboot the phone from recovery but it failed to boot and I was back in the recovery with the same error.
The way that I managed to boot the phone was to select to reboot into recovery (while being in the recovery), and then select to reboot the phone. That, for some reason rebooted the phone and it was able to boot into OS.
My 8T is full stock, with locked bootloader running OOS 11.0.5.6.KB05BA
Hope this is helpfull to someone.

I just received the same notification again. I am not sure if it is regarding the same update as yesterday because it was not applied, or if it is a new one. I have not tried to restart the phone.

I received the same notification but my phone restarted with no issues.
If you can back up the files from internal storage then do that and then flash OOS.

O wow. I'm glad that didn't happen to me either. I don't think you can reflash the OS. I sugget you back up everything just in case it doesn't want to restart later.

You can try manual update Google play system update from:
Security & Lock Screen --> Google Play system update
Btw, I had that notification yesterday, and for now everything is OK, and Google Play system update is "Septembar 1, 2020". Which version is yours?

I am on September 1, 2020. If I tap on it, it checks for updates and then says I need to restart to complete the update.

When I tap says, "your device is up to date"....

So I backed up the phone with the Oneplus Switch app. Copied the folder to my computer (had to zip it becaust the transfer was failing on a .jpg). Selected restart and was faced with the same issue. I restarted again from the recovery (without first rebooting to recovery as in the first post) and I saw a glimpse of the boot animation and then the phone restarted again. After that it booted into the OS and if I check for updated it says that the device is up to date.
Hopefully this will be the end of this issue.

the issue is the canary magisk and secure boot trying a different magisk version repatch boot img and boot it to flash it

I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.

bad pixel said:
I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.
Click to expand...
Click to collapse
You can try to download main-component apk from APKmirror, just download latest one (Januari), innstall it, and try redownloading the system update and restart. In my case, it restart just fine. And am on Cyberpunk H2OS 11.0.6.8, BL unlocked, Rooted

see the error, you may flash the third kernel.
just flash back the original boot img, and you can install Google Play System Update successfully.
you may suck in this error screen 1-2 times when reboot with third kernel, just exit and reboot, it will boot into system normally, don't worry.

Question Poco X3 Pro Bricked - Boots to Fastmode

I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.

crashykk said:
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
Click to expand...
Click to collapse
Reboot your phone and observe on the top part of the phone while there is the POCO logo showing.
1) If there is an unlocked lock icon on the top, you should be able to rescue with TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Type the fastboot code to get to TWRP again so you can flash ROMs.
Read here for ROM flashing tutorial.
https://forum.xda-developers.com/t/4288121/post-85137963
Step 16 is a must.
2) If you did not see this icon during booting POCO logo, chances are you accidently locked your bootloader with MiFlash. In this case, find Xiaomi repair center for warranty support.

I know how to flash a rom, but TWRP does not see my internal storage. Like it wasnt there.
edit:
I flashed Orangefox recovery and it did the trick. I was able to place some rom on internal storage and install it, but now i have 12 gb of storage instead of 233gb?
edit:2
I formated data and it went back to normal. Now i have my 256gb back.

I think you were encrypted, please read more online and follow rom flashing instructions. You didn't follow it that's why you were in trouble.

I flashed, rooted, unbricked a lot phones back in the Samsung S6 days. Even Redmi Note 5 Pro from xiaomi, but never heard of something like rom encrypting your access in recovery.
I didnt flashed custom roms on my Samsung s8 and s9, cuz they had fine software. MIUI 12 is so bad that I considered selling that Poco.

You didn't follow instructions, TWRP works perfectly fine. And the step you missed is Formatting Data partition after flashing ROM which decrypts it. (thus why you couldn't access internal storage or boot)
And you will run into same issue with OrangeFox aswell if you do the same mistake. Flashing procedure is a lot different in new smartphones.

I didn't follow, cuz I didn't know that flashing procedure is a lot different in new smartphones. I looked at it, it looked very similar, so I went with old habits. Now I know what to expect.