Related
Hello.
After recent acquisition of a Hannspad tablet i decided to install ubuntu desktop on it. Starting from the basics, clockworkmod was needed to be installed. As this tables is a replica of the gtablet , following this tutorial was mandatory. viewsonic-gtablet-for-dummies.webs.com
After installing clockworkmod from that tutorial for the 1.2 branch, i discovered that the softbuttons from the right side were broken, only buttons working for clockworkmod were the up/down (vol+, vol-).
So another recovery.img was neeeded. NVflash for nvidia tegra 250 was downloaded. When trying to understand the program, i issued the default command residing in a batch file, in the nvflash dierctory root " nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x3c000011 --create --go " ( still wonder why i did that ).
After this, the tablet became unresponsive, except for the apx mode. Only thing working was the power button. So i downloaded the bootloader for gtablet. After loading that bootloader, the tablet will start for half a second, but restart immediately. No recovery mode, no booting, just the backlights staying up for half a second.
My answer is, if anyone has any time and patience to help me and others who might encounter the thread, is there something that can be done to bring back the device?
Thanks !
yeah, you´ve 2 options : first you delete the partition and tell them you don´t know anything...
or install win 7/ or use ubuntu
Second option
RootRightUser said:
yeah, you´ve 2 options : first you delete the partition and tell them you don´t know anything...
or install win 7/ or use ubuntu
Click to expand...
Click to collapse
I don't think that win7 can be installed on an arm processor. As for ubuntu, i will try to install it, but i have to learn more about the post/storage/arm cpu in order to bring the tablet back to life.
Can anyone direct me to some resources on how to install an os on an arm architecture?
I tried to find the resources, but in no avail.
Thanks .
hmmm .. im really interested in this thread.
i also have this tablet and i would want to try some different roms but dont see any support for it anywhere (for the tablet).
hope u manage to recover ur device..
ill be watching this thread .
okay it´s easy....
download the update 4789 etc. from hannspree, rename just update, take zip file(update) into root of your external device than boot ( push volumen up+ and power button 5 seconds) than should the system reboot with old settings, if nothing happens try with ac adapter and usb.
@fxandrei : i try to install win 7,bootlloader etc. if you know something or have honeycombfiles/updates etc. pls say it thx
RootRightUser said:
okay it´s easy....
download the update 4789 etc. from hannspree, rename just update, take zip file(update) into root of your external device than boot ( push volumen up+ and power button 5 seconds) than should the system reboot with old settings, if nothing happens try with ac adapter and usb.
@fxandrei : i try to install win 7,bootlloader etc. if you know something or have honeycombfiles/updates etc. pls say it thx
Click to expand...
Click to collapse
Thank you, i will try as you instruct and come back with feedback.
good luck ..
@RootRightUser
i dont .
im looking for stuff like this.
im hopping that this tablet gets some support (like acer iconia or asus eee transformer).
Any news on it? I am on a worst scenario, the one where one decide to use nvflash_gtablet...zip on the Hannspad (modify partition scheme, and worst cbt )
I can't boot, or rescue anymore, and trying to recover the partition scheme seems to end in only APX mode to work (no more wolume up or down + power working)
Reflashing nvflash_gtablet restore viewsonic start screen but that's all...
I need a fresh and complete dump of hannspad SN10T1 (cbt+partitiontable+every partition dump)
For those interrested, with the help of people from slatedroid and forum.hardware.fr, I've been able to recover my tablet (not stock 12 patitions, but a good working 10 partitions images).
You can find instructions and the full package (rom 1.2.1-4789 + Linux and windows nvflash +drivers for windows + scripts) there:
I can't post URL so go to
www-DOT-slatedroid-DOT-com/topic/20148-hannspree-hannspad-sn10t1-rom-dump
For now, I can give you my Recovery for Hannspad (put you directly to 1.2.1-4789 Hannspree)
Instructions:
Connect your PC and Tablet with the usb cable
Put your device in APX mode.
APX mode is obtained, whe you have bricked your device, or when doing the following:
tablet is off and you start it by pressing and maintaining volume down + power button, it must power on and go to a black screen, it it goes to a freezed boot log or a work in progress image, the try wolume up + power button.
Linux:
You can see if your device in APX under linux by doing a lsusb, if you can see a line with:
Bus XXX Device YYY: ID 0955:7820 NVidia Corp.
So now you have a APX connexion with your tablet.
Download Recovery-SN10T1-1.2.1-4789.zip (link at bottom of post)
Extract it where you want, and execute ./nvflash_sn10t1.sh
After it is finished powerdown th tablet, do the opposite combo key (volume up or down + power for 3-4 seconds) and make a wipe data/factory reset.
You can restart, you have a stock rom (10 partitions only, not stock firmware)
Windows
Download Recovery-SN10T1-1.2.1-4789.zip
Extract it where you want
Now boot your tablet in APX mode:
APX mode is obtained, when you have bricked your device, or when doing the following:
tablet is off and you start it by pressing and maintaining volume down + power button, it must power on and go to a black screen, it it goes to a freezed boot log or a work in progress image, the try wolume up + power button.
Now connect your PC and the tablet by USB cable. Windows should search for drivers, it won't find it so you can cancel the windows update search. Now go to device properties (right click on computer and manage), and make it install the driver included in the zip. Now you must be able to execute nvflash_sn10t1.bat
After it is finished powerdown th tablet, do the opposite combo key (volume up or down + power for 3-4 seconds) and make a wipe data/factory reset.
You can restart, you have a stock rom (10 partitions only, not stock firmware).
Recovery-SN10T1-1.2.1-4789.zip file
dl DOT free DOT fr/fgw7CCws6
many thanks
Thanks, that fixed the problem. Although the tablet is working, the quest to have Ubuntu on the tablet is still on the table(some pun intended). On slatedroid forum there are some folks with the exact same ideea, so, let,s hope that running x11/Ubuntu on sn10t1 will happen.
Typing the message from the hannspad.
Cant boot into recovery
Hello'
Am sorry if I have posted this in the wrong thread.
I have a 53 version Hannspad and I was able to successfully install Flashback 7.2 onto it.
Everything was well until yesterday when I installed Rom Manager from the market and installed Gtab flash recovery by choosing first option in the rom manager and then selecting Gtab from the list (the list had Advent Vega' Elocity A7' etc).
It said "flashed successfully" and I almost forgot about it until yesterday when I decided to install fards Gtabcomb 3.3_refresh. Now I am unable to boot into either CWM recovery or stock recovery. The tablet boots and runs just fine just doesn't go into recovery. It says 'Recovery key detected' and gets struck though I can boot and use the tablet. I am writing this using the tablet. My main probelm with Flashback is that it doesn't allow me to download apps via market.
Please suggest me how to get CWM back.
Thank you
Help please! My device wont enter apx mode... it does open the recovery mode every time and i can't make modifications because the side buttons aren't working aswell.
I thank everybody for there hard work to get these problems solved, I do have a good one :
I tried to flash Recovery-SN10T1-1.2.1-4789.zip and it excuted ok on my hannspad I saw the Hannspree logo, than the Tap N Tap running logo .. but now the Hannspad didn't startup, it came in a loop of the Tap N Tap screen, after 4 times the screen became blank (only the green powerlight showing) .
Now I read i had to do a Data wipe (go into recovery mode) .. but After (hard) reboot and pushing the +/- button it just goes to APX mode and no recovery (stock nor CWM) i just can't seem to nvflash any recovery.img to make the thing work ..
I would love to have some help, i would really appreciate it
Sadly enough there isn't much of a Hpad community @XDA, so for help with your problem you might be better of in the [email protected] forums or, depending on your language skills at android-hilfe or hannspad.fr. All three have excellent recovery guides. Good luck.
You're a lifesaver!
kickinz1 said:
For those interrested, with the help of people from slatedroid and forum.hardware.fr, I've been able to recover my tablet (not stock 12 patitions, but a good working 10 partitions images).
You can find instructions and the full package (rom 1.2.1-4789 + Linux and windows nvflash +drivers for windows + scripts) there:
I can't post URL so go to
www-DOT-slatedroid-DOT-com/topic/20148-hannspree-hannspad-sn10t1-rom-dump
For now, I can give you my Recovery for Hannspad (put you directly to 1.2.1-4789 Hannspree)
Instructions:
Connect your PC and Tablet with the usb cable
Put your device in APX mode.
APX mode is obtained, whe you have bricked your device, or when doing the following:
tablet is off and you start it by pressing and maintaining volume down + power button, it must power on and go to a black screen, it it goes to a freezed boot log or a work in progress image, the try wolume up + power button.
Linux:
You can see if your device in APX under linux by doing a lsusb, if you can see a line with:
Bus XXX Device YYY: ID 0955:7820 NVidia Corp.
So now you have a APX connexion with your tablet.
Download Recovery-SN10T1-1.2.1-4789.zip (link at bottom of post)
Extract it where you want, and execute ./nvflash_sn10t1.sh
After it is finished powerdown th tablet, do the opposite combo key (volume up or down + power for 3-4 seconds) and make a wipe data/factory reset.
You can restart, you have a stock rom (10 partitions only, not stock firmware)
Windows
Download Recovery-SN10T1-1.2.1-4789.zip
Extract it where you want
Now boot your tablet in APX mode:
APX mode is obtained, when you have bricked your device, or when doing the following:
tablet is off and you start it by pressing and maintaining volume down + power button, it must power on and go to a black screen, it it goes to a freezed boot log or a work in progress image, the try wolume up + power button.
Now connect your PC and the tablet by USB cable. Windows should search for drivers, it won't find it so you can cancel the windows update search. Now go to device properties (right click on computer and manage), and make it install the driver included in the zip. Now you must be able to execute nvflash_sn10t1.bat
After it is finished powerdown th tablet, do the opposite combo key (volume up or down + power for 3-4 seconds) and make a wipe data/factory reset.
You can restart, you have a stock rom (10 partitions only, not stock firmware).
Recovery-SN10T1-1.2.1-4789.zip file
dl DOT free DOT fr/fgw7CCws6
Click to expand...
Click to collapse
I thought I had bricked my friends Hannspad for good after trying many other "solutions" until yours did the trick. Thanks for being both clever enough to know how to solve my problem and kind enough to share.
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
SP log files attached
thanks
elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
I'm not sure but i did find links for G730 official ROM.
There are 6 ROMs for this model, G730-U30, G730-C00, G730-T00, G730-U00 & more..
ROMs LINK
Then another link: Huawei G730-U00,Android 4.2,Emotion UI,V100R001CHNC17B137 Official Firmware
Seem's like there is stuff out there on internet, no offence. Just sharing information. Well, back to the bricked situation.... As i remember, there are methods to restore/fix semi/soft-bricked phone. Hope you find the solution. Search forum/internet.
I'm not an expert. Thats all i can share.
I have same problem.How to solve it.
same problem, what to do???
elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here
Hello, I came to this forums looking to get some help with a device that a friend gave me to fix. He tried to install some sort of custom ROM on his phone (Moto E XT1527), and after installing it, Im not totally sure what did he touch, but now the phone only boots up to a screen saying the following:
AP Fastboot Flash Mode (Secure)
BL: 80.0B (sha-2c9fcbc 2015-03-13 20:15:21)
Baseband: Not Available
Product/Variant: surnia XT1527 8GB P3
Serial Number: T00930M5JK
CPU: MSM8916 ES1. 0
eMMC: 8gb Samsung RV=07 PV=01 TY=57
DRAM: 1024MB Samsung S8 SDRAM DIE=4GB
Console [NULL]: null
Battery Ok
Device is LOCKED. Status Code: 2
Software status: modified
Transfer Mode: USB Connected
Click to expand...
Click to collapse
(There could be some sort of typo on it)
So far I have tried with a tool that suposedly would flash a ROM into the phone without typing any commands, but it failed at some point.
As for unlocking the bootloader, I was abble to obtain the code, yet when I try to unlock it via fastboot, it says that I need the permission to "Allow OEM Unlock", wich I can't grant because of the SO not booting.
Regarding to what my friend did with it, he's not sure, but he think he deleted some sort of file
Im not an expert on this kind of stuff, yet I can follow steps that are given to me to provide any info or to execute a fix, so I would appreciate any kind of help from you to diagnose and solve this problem
Thanks in advance
A little bump
Javier14 said:
Hello, I came to this forums looking to get some help with a device that a friend gave me to fix. He tried to install some sort of custom ROM on his phone (Moto E XT1527), and after installing it, Im not totally sure what did he touch, but now the phone only boots up to a screen saying the following:
(There could be some sort of typo on it)
So far I have tried with a tool that suposedly would flash a ROM into the phone without typing any commands, but it failed at some point.
As for unlocking the bootloader, I was abble to obtain the code, yet when I try to unlock it via fastboot, it says that I need the permission to "Allow OEM Unlock", wich I can't grant because of the SO not booting.
Regarding to what my friend did with it, he's not sure, but he think he deleted some sort of file
Im not an expert on this kind of stuff, yet I can follow steps that are given to me to provide any info or to execute a fix, so I would appreciate any kind of help from you to diagnose and solve this problem
Thanks in advance
Click to expand...
Click to collapse
it can be simply solved ....if you are able to boot to fast boot mode
HOW TO BOOT INTO FAST BOOT
First of all, you have to power off your Moto E.
In order to do so, press power button once and then select “power off” or keep pressing the power button for about 15 seconds.
Wait a few seconds until applying the next step.
After powering off your phone, press power button and volume down key at the same time.
Keep pressing these buttons for about 6, or 7 seconds.
Release the keys when the fastboot / bootloader mode is being displayed.
In fastboot use volume up and volume down keys in order to scroll up and down within bootloader menu and press power button in order to select your option.
if it enters fast boot mod unlock boot loaders ....when it says grant permission using volume up or down button
then flash a custom recovery ...make a factory data reset after you flash custom recovery .....
after all above steps flash any custom rom this will fix all your issues ... you can also try to flash stock rom images via fast boot
Adi Shakthi said:
it can be simply solved ....if you are able to boot to fast boot mode
HOW TO BOOT INTO FAST BOOT
First of all, you have to power off your Moto E.
In order to do so, press power button once and then select “power off” or keep pressing the power button for about 15 seconds.
Wait a few seconds until applying the next step.
After powering off your phone, press power button and volume down key at the same time.
Keep pressing these buttons for about 6, or 7 seconds.
Release the keys when the fastboot / bootloader mode is being displayed.
In fastboot use volume up and volume down keys in order to scroll up and down within bootloader menu and press power button in order to select your option.
if it enters fast boot mod unlock boot loaders ....when it says grant permission using volume up or down button
then flash a custom recovery ...make a factory data reset after you flash custom recovery .....
after all above steps flash any custom rom this will fix all your issues ... you can also try to flash stock rom images via fast boot
Click to expand...
Click to collapse
Hello and thanks for your answer. I have managed to get into fastboot mode, yet I still can't unlock the bootloader. It stills asks me to grant OEM permissions. Is there any way to grant it without booting into the SO?
Hi guys,
I currently have some issues with my beloved N5. I try to be as specific as I can (therefore the text will be a bit longer)
First things first: My device is experiencing the well known "stuck power button problem".
But I also do have problems which are not related to that one (at least thats what I believe).
Overview:
CM 13.1
ElementalX Kernel
TWRP on 3.0.20
Main issue: I can not start my phone regularly. When not plugged in, it just does not respond at all.
If it is plugged in I can get into the bootloader with only pressing Volume down (because the power button is stuck inside). Weird fact #1: in bootloader the power button should work to confirm a specific task like Start, or boot into recovery but it doesnt. Also: the phone is steady in the bootloader and does not keep rebooting.
Therefore I wanted to perform a backup (nandroid or at least all media) and reflash my ROM to see whether it is more of a software issue. I tried booting into TRWP which is not working (device shuts down after Google logo (might be because of the power button issue?).
I know that I can flash the recovery again through adb or the Nexus ToolKit but obviously I want to save my data first.
As far as I know there is no option as adb pull or through the recovery to save those only being in bootloader mode, am I right?
Question: Can I dirty flash without losing data? If thats not the cure, what else could help?
Other facts to know: while running
Code:
adb devices
I get that the
Code:
"adb server version (36) doesnt match this client (35): killing...
but then:
Code:
*daemon started successfully*
(same in Nexus Toolkit).
If I continue with
Code:
adb backup
it says: no devices / emulators found. Altough the nexus toolkit (and fastboot devices) say:
Code:
FASTBOOT: 03181238e07723e0 fastboot
If you made it until here thank you for reading :good: and I would be even more pleased if someone could help.
Best,
McRacoon
I have this problem to , i cant use my volume and power button in ROM / TWRP ,
I got lost, which data you want to save ?
fastboot flash boot recovery.img | fastboot reboot than gets you to recovery from where you can save data.
@Redchi: not really exactly my problem but if you can get into recovery you can use your touchscreen in TRWP?!
@icrunchbanger thanks for your reply.
I want to save all my data like videos, pictures, whatsapp chats etc.
I know how to flash the recovery (again). The question was whether I can save any data without a working recovery (just from the bootloader). Imo it is not possible but maybe you guys know how to do so.
If I reflash the recovery I still can not enter it as the phone reboots itself every 5 seconds due to the stuck power button. The reflashing operation is not finished (Nexus Toolkit says: "Waiting for your device" and times out after a while) and the battery icon pops up every 3 seconds.
Edit: and yes I tried several workarounds to unstuck the power button like flicking against the button, tapping on table, cleaning etc. The only thing I haven't done is tearing the motherboard apart and replacing the whole button itself.
I recommend removing the motherboard, applying pure alcohol around the area, and then quickly pressing and releasing the power button? If this doesn't work, I suggest replacing the power button.
i can use button to get bootloader + TWRP , but my Button volume up down and power cant use in Rom or TWRP, i do no this software or hardware ,? my nexus normaly use but not have button , I use mikey or double tab to wake get screen on , i use apk to get volume , sorry bad english
Good day, everybody!
So.. here's the deal.
I have a Samsung Galaxy A22, and it's been a while since I've seen the Android 13 update notification, but never had the time to do it (and I wish I never did).
Decided to finally do it on the 1st of January (yk, to start the year right!) and oh boy who knew I'd get stuck on a boot loop. I didn't even do a backup!
I've looked for countless how-to's online (on how to get out of the boot loop) and encountered people with my same problem: some advised to go into Recovery Mode and "Remove Cache Partition" and "Repair Apps". Managed to do it, no success.
Some say there's no way of saving the data if I want my phone back, but I've seen some glimpses of hope such as ADB and Fastboot or Odin Mode. Tried the first ones, but if I do "Reboot to Bootloader" I only get a black screen with an "Entering in Fastboot" in red.. and it stays stuck there, is it supposed to? I didn't really get how those work..
While for Odin Mode, I've been suggested to reinstall the OS, but not to downgrade since that would result in a factory reset.
Should I wait for the next android version, so that I can upgrade manually once it's out?
Also, by looking into Odin Mode I've found out about TWRP and how it comes with a working MTP connection and ADB enabled which allows you to extract almost all data stored on your device and even create physical images from them, as long as the device's bootloader (OEM?) is unlocked.
I looked for guides to unlock it buuut they all lead to my phone being on, which I can't do since my phone's on a boot loop.
So, in conclusion, here are my questions:
1- Are other samsung users here having my same issue?
2 - Is there a way, apart from the ones I listed, to get out of the boot loop without having to do a short reset?
3 - How do ADB & Fastboot work and how would they aid me into recovering my media?
4 - Can I unlock my bootloader while stuck on a boot loop?
Thank you everybody, hope someone out there knows a thing or two about this situation!!
EDIT 1:
Should anyone need a guide to samsung odin, I've found this very clear one! https://forum.xda-developers.com/t/...unked-noobs-guide-to-samsung-devices.4405681/
As for when I'll flash the next version, I've read that the next Android 13 update will come out with the Samsung S23, whose release date is expected during February 2023. Hopingly, it will soon be extended for other samsung phones as well! I'll make sure to update this thread once it does and how flashing it goes, since that's gonna be the final solution to us "bootlooped phoned" people! ;D
EDIT 2:
Good day everybody! Guess what? I've just found out Samsung has dropped a new firmware like, LONG AGO! Imagine the look of immense surprise in my face when I've seen it after "just wanting to check" moments ago!
Here's how it went:
I downloaded all the files needed from https://samfw.com/firmware/, the one I was looking for was A225FXXU3CWA6! Took a while, but totally worth it. All that was left was to put my phone in odin mode
(HOW TO ENTER ODIN MODE: turn off your phone (if in bootloop, do it forcefully by pressing power off & volume down simultaneously). connect your USB cable to your computer, but not your phone yet. now, press and hold the volume up and volume down buttons and at the same time, connect the USB cable to your phone)
Opened the ODIN3_v3.14.4 program on my computer, put the files accordingly (follow the guide I've mentioned in my first edit! USERDATA must be left empty & only put HOME_CSC where CSC is asked, if you wish to preserve your data!). NOW START!! Took 7:27 minutes!! AND EVERYTHING WAS STILL THERE! photos, music, videos, whatsapp messages, JUST THE SAME! and since it updated it was cooler too!
Patience truly is a virtue! <3 huuuuge thanks to alecxs (hope he doesn't mind me mentioning him!) for helping me through it all, and to the whole XDA community for existing, always eager to help! y'all are the best!! <3
Hope everyone who had my same problem can now sleep in peace and live happier haha!
nanawa said:
Good day, everybody!
So.. here's the deal.
I have a Samsung Galaxy A22, and it's been a while since I've seen the Android 13 update notification, but never had the time to do it (and I wish I never did).
Decided to finally do it on the 1st of January (yk, to start the year right!) and oh boy who knew I'd get stuck on a boot loop. I didn't even do a backup!
I've looked for countless how-to's online (on how to get out of the boot loop) and encountered people with my same problem: some advised to go into Recovery Mode and "Remove Cache Partition" and "Repair Apps". Managed to do it, no success.
Some say there's no way of saving the data if I want my phone back, but I've seen some glimpses of hope such as ADB and Fastboot or Odin Mode. Tried the first ones, but if I do "Reboot to Bootloader" I only get a black screen with an "Entering in Fastboot" in red.. and it stays stuck there, is it supposed to? I didn't really get how those work..
While for Odin Mode, I've been suggested to reinstall the OS, but not to downgrade since that would result in a factory reset.
Should I wait for the next android version, so that I can upgrade manually once it's out?
Also, by looking into Odin Mode I've found out about TWRP and how it comes with a working MTP connection and ADB enabled which allows you to extract almost all data stored on your device and even create physical images from them, as long as the device's bootloader (OEM?) is unlocked.
I looked for guides to unlock it buuut they all lead to my phone being on, which I can't do since my phone's on a boot loop.
So, in conclusion, here are my questions:
1- Are other samsung users here having my same issue?
2 - Is there a way, apart from the ones I listed, to get out of the boot loop without having to do a short reset?
3 - How do ADB & Fastboot work and how would they aid me into recovering my media?
4 - Can I unlock my bootloader while stuck on a boot loop?
Thank you everybody, hope someone out there knows a thing or two about this situation!!
Click to expand...
Click to collapse
I'm sorry to hear that your Samsung Galaxy A22 is stuck in a boot loop. Boot loops can be frustrating, but there are a few steps you can try to try to fix the problem.
Are other Samsung users having the same issue? It's possible that other Samsung users are experiencing similar issues with their devices after the Android 13 update. It's always a good idea to check for any known issues or bugs with a new update before installing it.
Is there a way to get out of the boot loop without a factory reset? One option you can try is to boot the device into Safe Mode, which will disable all third-party apps and allow you to determine if a third-party app is causing the boot loop. To boot into Safe Mode, follow these steps:
Turn off the device.
Press and hold the Power key past the model name screen.
When "SAMSUNG" appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
If the device is able to boot into Safe Mode without encountering a boot loop, it's likely that a third-party app is causing the problem. In this case, you can try uninstalling any recently downloaded apps to see if that fixes the issue.
How do ADB and Fastboot work and how would they help me recover my data? ADB (Android Debug Bridge) and Fastboot are tools that allow you to communicate with your Android device from a computer. ADB can be used to run commands on the device, install apps, and perform other tasks. Fastboot allows you to flash factory images, boot images, and other files to your device.
If your device is stuck in a boot loop and you can't access the Android operating system, you may be able to use ADB and Fastboot to fix the problem. For example, you might be able to use ADB to sideload a new version of the Android operating system, or use Fastboot to flash a factory image to your device.
Can I unlock the bootloader while stuck in a boot loop? Unfortunately, it's not possible to unlock the bootloader of your device while it's stuck in a boot loop. The bootloader must be unlocked while the device is powered on and fully operational.
In summary, there are a few steps you can try to try to fix the boot loop issue on your Samsung Galaxy A22, such as booting into Safe Mode or using ADB and Fastboot to sideload a new version of the Android operating system. However, if these steps don't work, you may need to perform a factory reset to fix the problem. Be aware that a factory reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Here are a few more steps you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Clear the cache partition: The cache partition stores temporary files and data, and sometimes these files can become corrupt and cause issues with the device. To clear the cache partition, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe cache partition."
Press Power key to select.
Press the Volume down key to highlight "yes" and press the Power key to select.
When the wipe cache partition is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Attempt to boot the device into Download Mode: Download Mode allows you to flash firmware and other files to your device using a tool like Odin. To boot into Download Mode, follow these steps:
Turn off the device.
Press and hold the Volume down key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys.
An warning screen will display. Press the Volume up key to continue.
The device will now be in Download Mode.
From Download Mode, you may be able to use a tool like Odin to flash a factory image or other firmware to your device in an attempt to fix the boot loop issue.
Try using a different charger or charging cable: In some cases, a faulty charger or charging cable can cause issues with the device, including boot loops. If you have access to another charger or charging cable, try using it to see if that helps fix the problem.
Contact Samsung support: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to contact Samsung support for further assistance. They may be able to provide additional troubleshooting steps or repair options.
I hope these additional steps are helpful!
Also, here are a few more things you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Check for any updates: It's possible that a software update may be available that can fix the boot loop issue on your device. To check for updates, follow these steps:
From the Home screen, tap the Apps icon.
Tap Settings.
Scroll to and tap Software update.
Tap Download and install.
If an update is available, follow the on-screen prompts to download and install the update.
Keep in mind that installing a software update may require a stable internet connection and enough storage space on your device.
Perform a hard reset: A hard reset, also known as a factory reset, will erase all data and restore the device to its original factory settings. This can be a useful option if the boot loop issue is caused by a software problem that can't be resolved through other means. To perform a hard reset, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe data/factory reset."
Press Power key to select.
Press the Volume down key to highlight "Yes -- delete all user data."
Press Power key to select and start the master reset.
When the master reset is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Check for any physical damage: In some cases, physical damage to the device can cause it to become stuck in a boot loop. If you suspect that your device has suffered physical damage, it's a good idea to have it inspected by a professional.
Consider seeking professional repair: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to seek professional repair services. A trained technician may be able to diagnose and fix the problem with your device.
With regards to this thread's title
Recover data with TWRP after device is stuck on boot loop?take note that you can recover user-data when phone gets booted into recovery mode ( Stock Recovery is good , TWRP isn't needed ) because in this mode you via ADB can pull the data you are interested in.
yeah welcome to bull****-bingo
(besides its fully restricted no adb) stock recovery doesn't have any access to /data at all. TWRP recovery does not support Samsung Encryption, no way to decrypt /data.
unlocking bootloader is no option as encryption keys are tied to the bootloader status and boot/recovery image signatures.
There is no way to access your data other than fix boot-loop and unlock screen.
install Odin3, download stock ROM at current bootloader level same as device (you can find on download mode screen) and flash HOME_CSC (instead CSC) to keep userdata partition.
if no HOME_CSC file exist, unpack files and flash partitions manually from mtkclient (do a backup before)
@Alecxs
it's not me who is the idiot here ... Take note that ADB is supported in Stock Recovery mode.
@nanawa
To boot into Stock Recovery mode ( Stock Recovery mode refers to Android's bootable partition in which the recovery console is installed ) on a Galaxy A22 5G is to use the physical buttons of the phone:
{
"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"
}
This is fairly straightforward. One needs to turn off the phone, press the required buttons and the phone will go straight to Stock Recovery mode.
Before one can run ADB commands in Stock Recovery mode ( one needs to have the proper ADB and USB drivers for the Galaxy A22 5G, as provided by Samsung, installed on PC ) one of course must have phone initially unplugged before entering Stock Recovery mode. When phone is started in Stock Recovery mode one has to connect phone with PC via USB-cable and start USB-Debug mode - AKA ADB.
In USB-Debug mode you even can start an Android shell and remove any encryption as shown next
Code:
mkdir C:\DCIM 2>nul
adb devices
adb shell "su && echo '--set_encrypted_filesystem=off' > /cache/recovery/command"
adb pull /sdcard/DCIM C:\DCIM
dir C:\DCIM | more
you don't have any android device running android 5+ otherwise you would know that in stock recovery adb is limited to one single cmd that is called sideload
what you can do with adb in stock recovery is NOTHING
also your "remove" of encryption is bull****. data cannot decrypted without credentials not even with root lol.
what you're referring to is cmd (on /cache partition) to disable encrypted fs (requires formatting), used only for OTA update zip unrelated to adb (and unrelated to decryption)
maybe it works on your ancient android emulator but that's different from android smartphones. do not provide "solutions" you haven't tested yourself.
To keep you updated:
When running recovery image from debuggable builds (i.e. -eng or -userdebug build variants, or ro.debuggable=1 in /prop.default), adbd service is enabled and started by default, which allows ADB communication. A device should be listed under adb devices
adb devices
List of devices attached
1234567890abcdef recovery
Although /system/bin/adbd is built from the same code base as the one in the normal boot, may be for most only a subset of ADB commands are meaningful under recovery, such as adb root, adb shell, adb push, adb pull etc. Since Android Q, adb shell no longer requires manually mounting /system from recovery menu.
which device you have tested was able to run adb root, adb shell, adb push, adb pull in stock recovery?
which device is released as eng or -userdebug build? name a single one
bonus: which stock recovery is able to mount encrypted /data (and how the lock screen pattern is requested without touch screen)?
of course, you have no proof and no arguments, as always...
https://forum.xda-developers.com/t/retrieving-files-from-internal-memory.4523487/post-87905167
ChristianMorris said:
Also, here are a few more things you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Check for any updates: It's possible that a software update may be available that can fix the boot loop issue on your device. To check for updates, follow these steps:
From the Home screen, tap the Apps icon.
Tap Settings.
Scroll to and tap Software update.
Tap Download and install.
If an update is available, follow the on-screen prompts to download and install the update.
Keep in mind that installing a software update may require a stable internet connection and enough storage space on your device.
Perform a hard reset: A hard reset, also known as a factory reset, will erase all data and restore the device to its original factory settings. This can be a useful option if the boot loop issue is caused by a software problem that can't be resolved through other means. To perform a hard reset, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe data/factory reset."
Press Power key to select.
Press the Volume down key to highlight "Yes -- delete all user data."
Press Power key to select and start the master reset.
When the master reset is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Check for any physical damage: In some cases, physical damage to the device can cause it to become stuck in a boot loop. If you suspect that your device has suffered physical damage, it's a good idea to have it inspected by a professional.
Consider seeking professional repair: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to seek professional repair services. A trained technician may be able to diagnose and fix the problem with your device.
Click to expand...
Click to collapse
Thank you a whole lot for taking the time to write all this, means a lot to me Christian!
But.. I can't manage to get into Safe Mode. I believe it's because it isn't a third-party app triggering the boot loop (since it all started with the update and solely because of it) but I might be wrong, as I'm not quite familiar with how that works.
As for the cache partition... I tried, but it didn't change anything
"Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding." Does this mean I can still make that backup, even if my phone's on bootloop?
Also.. you advised to use ADB, but can I do that if the bootloader wasn't unlocked in the first place?
Again, thank you so much for replying, truly!! <3
xXx yYy said:
With regards to this thread's title
Recover data with TWRP after device is stuck on boot loop?take note that you can recover user-data when phone gets booted into recovery mode ( Stock Recovery is good , TWRP isn't needed ) because in this mode you via ADB can pull the data you are interested in.
Click to expand...
Click to collapse
Thank you for correcting it!
As for "stock recovery", would you please elaborate? that's the first I'm hearing of it!
aIecxs said:
yeah welcome to bull****-bingo
(besides its fully restricted no adb) stock recovery doesn't have any access to /data at all. TWRP recovery does not support Samsung Encryption, no way to decrypt /data.
unlocking bootloader is no option as encryption keys are tied to the bootloader status and boot/recovery image signatures.
There is no way to access your data other than fix boot-loop and unlock screen.
install Odin3, download stock ROM at current bootloader level same as device (you can find on download mode screen) and flash HOME_CSC (instead CSC) to keep userdata partition.
if no HOME_CSC file exist, unpack files and flash partitions manually from mtkclient (do a backup before)
Click to expand...
Click to collapse
Oh my, I think I'm understanding less and less..
Does this mean ADB can't help?
Regarding the "current bootloader level same as device" I can find on the download mode screen.. I don't get what I'm supposed to look for, I attached a pic of the screen I get, if you may be so kind to tell me what to do!
xXx yYy said:
@Alecxs
it's not me who is the idiot here ... Take note that ADB is supported in Stock Recovery mode.
@nanawa
To boot into Stock Recovery mode ( Stock Recovery mode refers to Android's bootable partition in which the recovery console is installed ) on a Galaxy A22 5G is to use the physical buttons of the phone:
This is fairly straightforward. One needs to turn off the phone, press the required buttons and the phone will go straight to Stock Recovery mode.
Before one can run ADB commands in Stock Recovery mode ( one needs to have the proper ADB and USB drivers for the Galaxy A22 5G, as provided by Samsung, installed on PC ) one of course must have phone initially unplugged before entering Stock Recovery mode. When phone is started in Stock Recovery mode one has to connect phone with PC via USB-cable and start USB-Debug mode - AKA ADB.
In USB-Debug mode you even can start an Android shell and remove any encryption as shown next
Code:
mkdir C:\DCIM 2>nul
adb devices
adb shell "su && recovery --set_filesystem_encryption=off"
adb pull /sdcard/DCIM C:\DCIM
dir C:\DCIM | more
Click to expand...
Click to collapse
Okok, now I get what stock recovery mode is.. I thought it was a new thing :')
So, once in stock recovery, do I just run ADB and copy paste the code you wrote?
As for the rest of the discussion I can't understand a single thing, can I or can I not retrieve data with ADB? @aIecxs @xXx yYy
Also this might be dumb to say but regarding "and how the lock screen pattern is requested without touch screen)?" my phone's also locked by finger pattern! if that makes sense (also idk why I'm writing in bold I'm so new to this.. but please don't fight folks, I appreciate the help you're both giving me!)
no worry, you're not the only one who doesn't understand much...
on PC download platform-tools then connect device in recovery mode and install usb drivers. now add platform-tools directory to path (or navigate to directory with 'cd') in cmd.exe
if adb is available you should see device serialno when typing 'adb devices'. that's all, the rest won't work (but please try anyway, just to proof him wrong xD)
RP SWREV: B3 means bootloader level = 3
bootloader is downgrade protected, so even in case you manage to flash ROM with lower bootloader level (for example with mtkclient) device won't boot.
you can only flash ROM with same or higher bootloader level because of downgrade protection.
kindly upload picture of recovery mode screen too, so we can check for official ROM that matches best.
nanawa said:
As for the rest of the discussion I can't understand a single thing, can I or can I not retrieve data with ADB? @aIecxs @xXx yYy
Click to expand...
Click to collapse
Because you tagged me:
1. When device got booted into Recovery mode, a stripped down version of Android is loaded
what allows to perform basic tasks - this is comparable with WinRE what is based on Windows PC's recovery environment that exists by default on all Windows PCs .
2. When booting Android device into Recovery mode device's /data partition doesn't get mounted, thus no locks are got activated.
3. According to source-code of file recovery.cpp what is part of AOSP v13
/** The recovery tool communicates with the main system through /cache files.* /cache/recovery/command - INPUT - command line for tool, one arg per line* /cache/recovery/log - OUTPUT - combined log file from recovery run(s)** The arguments which may be supplied in the recovery.command file:* --update_package=path - verify install an OTA package file* --install_with_fuse - install the update package with FUSE. This allows installation of large* packages on LP32 builds. Since the mmap will otherwise fail due to out of memory.* --wipe_data - erase user data (and cache), then reboot* --prompt_and_wipe_data - prompt the user that data is corrupt, with their consent erase user* data (and cache), then reboot* --wipe_cache - wipe cache (but not user data), then reboot* --show_text - show the recovery text menu, used by some bootloader (e.g. http://b/36872519).* --set_encrypted_filesystem=on|off - enables / diasables encrypted fs* --just_exit - do nothing; exit and reboot*
Click to expand...
Click to collapse
any encryption can get disabled, thus all user-data beome fully readable: as I've shown some posts above this can be achieved running an ADB command whilst in Recovery mode.
DO NOT TAG ME ANYMORE BECAUSE I NO LONGER PARTICIPATE THIS THREAD.
despites that's all hypothetical (you never tested you just defend your fantasy) that requires root permissions to write on /cache (we don't have) furthermore 'disabled' is nothing else than 'destroyed' in that context and requires formatting. in no way the data can be decrypted/accessed like that (as already stated)
again, in stock recovery no adb commands work.