Database Info

[Q] HTC Incredible possibly bricked

Everything works except the bootloader. I use quick boot and go to bootloader. When I go to factory reset, ( your suppose to push power button as accept) it will bring me back to the main page of the bootloader. On all other options other than the reset I can move up and down on main page, but when I click factory reset, it brings me back to main page and is stuck on the fastboot option. If I click the power button to normally proceed, it freezes then i have to pull the battery. Idk if the rom that I currently have is out of date and had failed somewhere, seeing I have had it for about 3-4 months( Incredibly re-Engineered)
If someone could help me, I'd greatly appreciate it

Someone help me out

[Q] xoom not powering on

Hi
After being on numerous custom Roms for the xoom I decided to return to stock and was succesful in return to the 3.01 stock image for the wifi MZ604 model
I was also successful in relocking the xoom.
I then began to receive the offical updates though everytime the were applied I had to go into recovery and wipe the device as otherwise it would bootloop on the dual core screen.
On the last update that it received and that was installed , on rebooting nothing happend and the screen just went blank
No combination of volume up + power would show any sign of doing anything.
After leaving the tablet to the side for awhile I noticed it came up with the following
model mz604 : Revision0 (0x8000) modem none
InitBl Info function failed with codes 299/3
failed to boot 0x0001
starting RSD mode 3
one wire : charger is not connected or battery is not being charged
battery charge level : 56%
I tried fastbooting and adb at this point but no devices are found. However when plugging in the xoom my laptop recognises something is attached.
After some searching I found out about RSd lite and SBF files.
When opening rsdlite v5.6 (running as admin) the tablet is recognised and I have now attempted to use two sbf files
HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF.sb f
and
HUBWF_W5.H.6.2-24_SIGNED_UCAHUBLWFRTCOREEU_P006_A006_M003_HWwifi_hubble_Service1 FF.sbf
however both fail when it attempts re numeration.
I would greatly appreciate any help that anyone could give on this
Thanks

Try this.
My mom's Xoom had a similar problem. Reboot the tablet by pressing Volume Up and Power.
Then quickly turn on the xoom and press the down button as fast as possible, and continue pressing until you see "Recovery Mode" (or something similar) on the top left of the screen.
Once you see that, press the volume up button. Quickly, when you see the Android guy with the exclamation mark tap the power button and the up button.
This will take you to recovery mode. In there use the up and down volume keys to navigate and the power button to confirm things.
Go down to restore/delete data (may vary) and press power. use the volume down key to scroll to Yes.
This will restore your tablet back to factory settings. If you're trying to backup your data, don't try... No such luck and you won't be able to without the tablet booted.

thanks for the reply but this didnt work. Tried quite a few times. The screen just goes blank and again after a long while the error shown in the op appears. Should add there is no Motorola logo showing.
I have also tried forcing fastboot by the instructions found in other similar threads but again this does not work.
I think my best bet is the SBF files , but need to understand why this is failing on re-numeration

Coby Kyros MID7010 (MID 7010) FACTORY RESET, Rooting, Android Market

Below is the procedure to FACTORY REST, ROOT AND MArket installation for COBY KYROS MID7010 or MID 7010 Tablet owners stuck at white boot screen OR android OS not loading after any manipulation with the firmware OR interested in rooting and installing google market.
FACTORY RESET Steps:
1. Turn OFF the device
2. Make sure its turned OFF
3. Press and hold simultaneously POWER + BACK + HOME buttons (as in third Pic)
4. The device turns on with COBY logo, keep pressing......
5. After about 15 to 20 seconds the COBY LOGO display changes and prompts to press the keys again within 5 secs to factory reset the device.
6. LEAVE the power button now while still pressing HOME and BACK keys
7. FActory reset is initiated!
TO INSTALL MARKET AND ROOT:
1. Enable adb debugging on your tablet,connect to pc wait for driver installation if any. Run SuperOneClickv2.3.2-ShortFuse.zip > choose advance> driver install
2. Will prompt to force install drivers ( if the adb device drivers not available), accept and sit back! the program will not respond for a while 10-15mins and prompts back that the drivers are installed.
3. Run root from the above software (clicking root tab)
4. Open root explorer or any file browser accepting root, browse to system/app copy all files in attached folder (apks) here, if prompts to rewrite( do not allow!)
5. Change permissions of the copied files as in other apks in system/app folder.
6. Google market app appears in app drawer.
7. Run and Enjoy!

thnks for the useful thred
thanks a lot for this thred since no one is taking care of this model "7010" .. my kyros 7010 stop working and freez on android booting screen a did the method you post here but i got this message
" Unexpected updater mode! Pleas reboot your device"
could you pleas support me with any help since i am olmost about to lose the hope to get my Kyros back to life

Follow the buttons, you arent pressing hard the back button. its HOME + BACK+POWER all three buttons altogether. until the coby screen changes to reset request as in pics. Ask someone to press the power button while you press the front two. UNTIL THE COBY LOGO display changes (15 to 20 seconds).

the same problem
really i tryed it ten times and got the same message " unexpectaed updater mode please reboot your device"
it gives me Penguin logo "Linux logo" befor this message - this logo is normally comes even befor it stop working

pressing the power button + home button only displays your message. You are definitely not pressing back button hard enough or its broken?!?. TRy pressing power than reset pin at back together. a white screen appears release both buttons and try the three button combination again.
YOU must apply steady pressure on the three buttons for 20 seconds till the coby logo screen automatically changes. Ask someone else to help you with it. THIS KEY COMBINATION DEFINITELY WORKS!

the same problem
i did the power + reset and yes it gives me a white screen then use the three buttons "i am sure i pressed them well"
the coby logo screen changes to Penguin logo "Linux logo" and it gives me the same message
i feel that i am breaking your head but you are the only hope that i have no more help on this model .. so can i do that throw ADB i did root it using adb and whin i tybe # recovery it gives me (android system recovery <e3>) with 3 choces to restor or reboot somthing like that but non of them are working i can choose between them but i cant select or confirm i tried all the buttons but no action

when do you release the three buttons? Are you sure its mid 7010 there is no recovery rom partition in mid7010 as far as i know.

i releas them after i swe the message "unexpectaed updater mode please reboot your device" and i try to wait more than one min as well
and yes i am sure it is coby kyros MID 7010. i got it from Dubai as a present
i know there is no recovery partition as i read it a lot on the internet.
so do u have any recovery rom for that model or any other way to install system on it???

Since there is no recovery partition than A kernel is required to repartion the partition table WHICH IS NOT EASY and since there is a way to factory reset why would one bother. i don't understand how you got to recovery menu when there isnt any? Besides have retried the steps and they work all the time. MOSt probably your return key is damaged!

rooting
i did everything and then when i connect the device via usb (after debugging n since there is no unmount) superoneclick does nothing, no driver update nothing, it just stays there, n if i click root, it hangs(super). m i doing something wrong?

it hangs! thats the point..... it takes time. Does it prompt to force install drivers yes:no?
the program will not respond for a while
Click to expand...
Click to collapse
Where does it freeze? ADB kill server> ADb start server>?

stuck on android logo after factory reset
mughalgxt said:
when do you release the three buttons? Are you sure its mid 7010 there is no recovery rom partition in mid7010 as far as i know.
Click to expand...
Click to collapse
Hi, i also have the same problem. Im stuck on the android logo after i did a factory reset. I tried the three button combo u instructed but im stuck always on the coby logo if i hold the three button.
Any help will do. Thank you

kernel
mughalgxt said:
Since there is no recovery partition than A kernel is required to repartion the partition table WHICH IS NOT EASY and since there is a way to factory reset why would one bother. i don't understand how you got to recovery menu when there isnt any? Besides have retried the steps and they work all the time. MOSt probably your return key is damaged!
Click to expand...
Click to collapse
aftry month now of trying every thing to get this kyros to life again but failed ... i think as u said a kernel is the only hope now .. hope i found some one to help in how can i do that

magus1982 said:
Hi, i also have the same problem. Im stuck on the android logo after i did a factory reset. I tried the three button combo u instructed but im stuck always on the coby logo if i hold the three button.
Any help will do. Thank you
Click to expand...
Click to collapse
You have to keep holding the three buttons the Coby LOGO display will change after 20-30 secs. ANDROID logo means the reset is done and the OS is loading will take time after reset. blank black screen means the Os cannot load hence factory reset must be done. Which logo are you stuck with?

sherif.afifi said:
aftry month now of trying every thing to get this kyros to life again but failed ... i think as u said a kernel is the only hope now .. hope i found some one to help in how can i do that
Click to expand...
Click to collapse
Your final hope is getting the back button repaired or ask someone else to do the reset procedure for you. No one is going to create a kernel for you. or for coby. try kyros forum website see if you persuade someone for more TECHNICAl support. I believe your tab's back button is damaged.

I have the Coby Kyros MID7010wc and I followed those steps, but it didn`t work - google market icon didn`t show up on apps screens. I tried to run those apks but it always says "application is not installed".
Is there something else that I can do?

did you root the device successfully?
how did you change the permission of the files in the attachment after pasting them into /system/app folder?
did you restart the device after above step?
* You need not manually install anything as it wont work just copy and paste them into system/app, change permissions and restart.

Yes it is rooted - used SuperOneClick
I didn`t understand when you said "if prompts to rewrite( do not allow!) "
if I don`t overwrite the apks it won`t install the files.
Anyway, used root explorer and copied each apk one by one in the system/app folder then changed the permission (checked every fields).

Did you reboot the system after changing permissions? Overwriting all apks in the attachment to system/app is not required rather unnecessary as google framework already exists only missing is phonesky or android market. These steps worked for me try reading other mid7xxxx threads to cross check

I redone everything and it is working as expected.
thanks!

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..

bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

Glad you're out of boot loop.

Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.

Pixel 4a stuck in bootloop

I have a pixel 4a with stock rom and recovery that is boot looping after an update. The device has a couple pictures I would like to recover and I was hoping I could use adb to pull those files from the device. The device does have a passcode that I know and and I am able to boot into resuce mode and run "abd devices", and it shows the device in rescue.
When I try to run, "adb shell ls, I get "error:closed"
I tried abd pull "/sdcard/DCIM" and received, "adb: error: connect failed: closed"
Any help is greatly appreciated!

This might be an obvious question, but have you tried booting up in safe mode?

JohnC said:
This might be an obvious question, but have you tried booting up in safe mode?
Click to expand...
Click to collapse
I read holding the power button and tapping the logo was the shortcut but that did not do anything. How do you boot it in safemode?

I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Edit: Important: Safe mode removes some Home screen widgets.

JohnC said:
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Click to expand...
Click to collapse
I found that as well and just tried it a dozen times and I never get any safe mode idication at the bottom the screen. I only get a Google logo with a progress bar that never finishes.

What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)

JohnC said:
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
Click to expand...
Click to collapse
Its running Android 11
It shows 11/RQ2A.210305.006/7119741 in recovery mode. It would have been up update pushed just before 4/4/21. I think it was security updates but I do not know how to verify that. My other Pixel 4a phone updated last around that same time and shows 11/RQ2A.210405.210305.005

This unfortunately is now outside of my experience, so I would be just guessing at this point.

So I was able to get into fast boot and use the flash utility provided by Google and Google chrome to detect the device, but when I try to flash it with sunfish i get an error about "oem unlocking" but I will have to dig further tomorrow. Hoping that I can get it to do something.

That error might be because your bootloader is locked, so it can't flash a new boot image to it.
The only way I know to unlock it is from the developer options in the settings, but that would require the phone to be able to bootup.

Adb sideload the stock OTA in recovery

Glad to hear that