Related
Dear XDA Developers,
As a new member of this amazing thriving community, I tried to root my device, a first time experience for me. Being one of those people who does not exactly read manuals or instructions, I happened to learn how to do about 99% of rooting, with a fatally wrong one percent. I lost my device and have now been pressing buttons, and doing all kinds of stuff, incluing the following, teenybins, recovery mode, deleting everything (this was probably my biggest mistake as I lost my recovery). Let me start from the beginning, I originally set up a recovery with Clockworkmod's helium, and then installed Clockworkmod's ROM Manager, after thinking I had rooted my phone through command prompt. I had not. After quite a few errors when it tried to install the Recovery I tried to also install TWRP. Then, I went and reset it to the factory settings, and rerooted using another tool, also don't remember exactly which one, since I had to try multiple times, with multiple different rooting softwares before it worked. Then, I installed Clockworkmod Recovery, seemingly successfully, moved CM 10.2 RC onto my phone, and the corresponding google apps package. I tried to install both, but I came across the Rom Manager saying I could only install one zip file at a time, which led me to only try to install CM 10.2 RC, thinking I could later download the google apps package. My phone then turned off, and upon restarting, it said Secure Boot error, and some other text, whatever I tried. Then upon searching for an hour or so, I found a website talking about teenybins, on XDA, which I followed to the letter. http://forum.xda-developers.com/showthread.php?t=2249500 . During this, at first, my computer said that the usb was not recognized, so I got AutoLGNPST-tSilenzio, which allowed me to get LGNPST working. I then proceeded with the instructions, and everything went to plan, and it stopped at 67%, then went to 85% as I disconnected my phone. Then, it showed a white google logo, with an unlocked lock. For a while, I could not get it to do anything, but then I got it to go to download mode again, and redid the process in hopes of the second time working. It did not. however, after this, by holding the power and the raise volume buttons, I got to an android laying down, with its stomach open, A big green start arrow pointed at my power button, two arrows, up and down, by my volume buttons, and the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 32 GB
HW VERSION - rev_11
BOOTLOADER VERSION - MOKOZ10f
BASEBAND VERSION - N/A
CARRIER INFO - None
SERIAL NUMBER - 018e8dcb52d6a343
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Then I played around with it, in recovery mode, not really doing anything, wondering why It was TWRM instead of CWR, until I finally got ADB working, upon which I first tried Sideloading CM 10.2
Which resulted in the following:
Starting ADB sideload feature. . .
Installing '/data/media/sideload.zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
It also says adb sideload complete, with a red Failed underneath, and has one option below, to reboot system
and then I pushed CM 10.2 along with google apps, onto my phone, and tried to install. which resulted in the following:
Uploading partition details . . .
E: Unable to mount '/system
Installing '/sdcard/cm-110.2.0-RC1-E975(1).zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Error Flashing zip '/sdcard/cm-110.2.0-RC1-E975(1).zip'
Uploading partition details. . .
E: Unable to mount '/system
Installing '/sdcard/apps.zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
************************************************
Google Apps for Android 4.3.0
************************************************
Installing files. . .
Cleaning up. . .
Installation complete!
Installing '/sdcard/cm-110.2.0-RC1-E975(1).zip'. . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Error Flashing zip '/sdcard/cm-110.2.0-RC1-E975(1).zip'
Uploading partition details. . .
E: Unable to mount '/system
And below the command window, it says failed, and three actions, home, reboot system, and wipe cache/dalvik, of which I have tried all three, which all work.
I understand I may not be the smartest person to make such a litany of mistakes, but I hope that some of the great developers here could somehow help unbrick my device, as I have no way to get a new (smart)phone in the next year, so this is really my only hope. If someone could please tell me how to fix it, with phone terminology explained, but I have no problems using any command prompt or any other methods, as I do do a lot of work with computers. Thank you in advance for what I know will be a good reply, and I wish you all a good day.
PS: Could someone please tell me how to successfully flash CM from where it ends up as I could not find a way from stock except for the one that led to this unfortunate situation.
@kimitza
This post is your farewell. Help him out
Sent from my LG-E975 using Tapatalk
)...like i said, some like to complicate the simplest things.If you can still enter download mode(turn off phone, pres vol down and plug the phone to pc)...use kdz updater to flash a stock rom.
And click the damn FAQ thread,i don't know how i could simplify it more.Rooting is easy,but,if there are so many ways to root, there is ONLY ONE WAY TO UNLOCK THE BOOTLOADER AND FLASH CWM. Don't play smartass and try anything else than FREEGEE...it can be done,but the hell would someone try to unlock with adb,when this magical app is available(kudos shelnutt2).?
Reply
kimitza said:
)...like i said, some like to complicate the simplest things.If you can still enter download mode(turn off phone, pres vol down and plug the phone to pc)...use kdz updater to flash a stock rom.
And click the damn FAQ thread,i don't know how i could simplify it more.Rooting is easy,but,if there are so many ways to root, there is ONLY ONE WAY TO UNLOCK THE BOOTLOADER AND FLASH CWM. Don't play smartass and try anything else than FREEGEE...it can be done,but the hell would someone try to unlock with adb,when this magical app is available(kudos shelnutt2).?
Click to expand...
Click to collapse
@kimitza I do appreciate the information, but for the life of me, I cannot find a working kdz file, I am a starhub customer in singapore, because it always says Access denied to the file. On top of this, the other file I tried which was in the instructions I found, ends up with Error LParam: 100 WParam 72, and switches from download mode to that little laying down android if I attempt to start the upload. Could you please give a working link or file, and possibly more precise instructions, or a link to some
http://lg-phone-firmware.com/
if one is not available try other. open europe ones work just fine.
seems you are on nexus bootloader, if thats true, when while using kdz you turn to bootloader, simply either using volume keys return to download mode or manualy turn to download mode it will resume.
sorry forgot what exactly i did. not on custom rom for some time now.
there is a small tool,called kdz downloader. insert the imei and that tool will automagically find the latest firmware available for yout phone....
It's also in my FAQ.
Symptoms:
1. Boot loop. GT-N7102 logo comes and the device reboots.
2. Can go to download mode. Model no. GT-N7102 is visible
3. Recovery mode-Android shows up for ~4 seconds and then phone reboots and goes into a boot-loop.
Was running N7102ZCUEOJ1_JB43_deodex_gapps_root_noknox_lite_by _neopunk88 (since March'16), when the phone suddenly decided to go into a boot-loop.
The phone was rooted. I had installed LSpeed the previous night and had set it to run in recommended mode.
What I have tried so far
1. Odin 3.07, 3.09 etc
2. stock recovery flash fails
2. tried to flash N7102ZCUEOJ1_N7102CHNEOJ1_N7102ZCUEML1_HOME.tar.md5 (last stock), but fails
3. After I had exhausted possibilities, tried the following pit files, one at a time, first from here and then here and then here along with the stock ROM. All pit files seem legit and the correct ones, but I have no way to verify. I have tried first without and then with re-partition option selected in Odin. Flash fails.
4. All drivers, USB ports and cable okay as I can flash my wife's S6.
Phone still going into download mode.
Odin fail modes
1. without pit file, while flashing either recovery or stock rom, Odil fails just after sboot.bin at NAND write-start.
2. with pit file and re-partition checked, Odin gets stuck in "get pit file for mapping"
3. with pit file but re-partition unchecked, Odin fails is the same as (1)
4. I have tried setting Odin compatibility to XP but it does not result in anything different. I haven't needed xp compatibility setting this while flashing anything before.
Please could I have some guidance on what options I have left and the files, if I am not using the correct ones?
My belief is that if I can get to the download mode, there has to be way to un-brick the phone..fingers crossed.
Thanks in advance.
UPDATE: Fixed phone by replacing the motherboard from here. Everything working fine now.
still waiting for a response..
@jam_27 It is possible that eMMC got corrupted. (it's a hardware fail)
If I were you I would try to flash TWRP. http://www.twrp.me - For N7100, as it doesn't matter for recovery.
READ: http://forum.xda-developers.com/galaxy-note-2/help/nt7100-wont-boot-wont-charge-recover-t3504290
Thanks, TWRP recovery flash fails at NAND write start.
jam_27 said:
Thanks, TWRP recovery flash fails at NAND write start.
Click to expand...
Click to collapse
Below the JTAG tool report from FoneFunShop UK
eMMC Flash Memory Chip is damaged
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
----
I wont be able to replace the emmc chip myself (don't have the correct tools) but should be able to replace the motherboard.
Any other suggestions before I open up the until.
Galaxy a70 a705fn stuck on partition
<!>
boot reason boot : hash of data does not match digest in description . (2nd) (3)
Calculated hash of (boot) : F5877D7EDC. (VEMETA) : 98EEF63C0
SAMSUNG boot. A706FNXXU5BTE3, 31342670R
VBMETA A705FNXXU5BTC2, 296911020R
Plz i cant flash stock firmware now it happened after a minor update
Same here but with the following parameters:
boot reason boot : hash of data does not match digest in description . (2nd) (3)
Calculated hash of (boot) : A7681EDC3D. (VEMETA) : 98EEF63C0
SAMSUNG boot. A705FNXXU5BTF1, 31708158R
VBMETA A705FNXXU5BTC2, 29691020R
Also after a minor update, please help!
NB: Phone was rooted but later flashed official ROM but left bootloader unlocked.
winterxda said:
Same here but with the following parameters:
boot reason boot : hash of data does not match digest in description . (2nd) (3)
Calculated hash of (boot) : A7681EDC3D. (VEMETA) : 98EEF63C0
SAMSUNG boot. A705FNXXU5BTF1, 31708158R
VBMETA A705FNXXU5BTC2, 29691020R
Also after a minor update, please help!
NB: Phone was rooted but later flashed official ROM but left bootloader unlocked.
Click to expand...
Click to collapse
I used the following solution which I found on a Samsung forum and it worked!
:good::good::good:
Hello Every One,
I had the same issue after trying to update my A70 phone based on a message which poped up from samsung asking me to update.
A friend of mine managed to resolve my issue without losing any data using that method:
1st : from the error msg --- > last line you will find the firmware version ex: A705FNXXU4ASK6
2nd: Goto https://www.sammobile.com/ --> Devices --> Choose your model --> Firmware --> Choose your country and download the firmware. (Download it and unzip it)
3rd: Download a software called Odin and follow the instruction ( MAKE SURE TO UNCHECK RE-PARTITION FIELD FROM OPTIONS TAB) IF YOU WANT TO KEEP YOU DATA
4th: In my case i have a new model so i uploaded the following 4 files ( BL , AP , CP , HOME_CSC) after i pluged the cable.
Dont forget to uncheck the Re-partition.
Click Start
winterxda said:
Same here but with the following parameters:
boot reason boot : hash of data does not match digest in description . (2nd) (3)
Calculated hash of (boot) : A7681EDC3D. (VEMETA) : 98EEF63C0
SAMSUNG boot. A705FNXXU5BTF1, 31708158R
VBMETA A705FNXXU5BTC2, 29691020R
Also after a minor update, please help!
NB: Phone was rooted but later flashed official ROM but left bootloader unlocked.
Click to expand...
Click to collapse
It locked my boot loader And I was previously fully rooted Now I’m stuck on the blue screen
My tablet starting you shut off for 30sec then come back on. Then it started to this **** completely off and reboot and they will get to the home screen and when I would soon as I would open an app it would reboot all over again and I did it over and over and over then I was trying to clear the chase and somehow it did this and I was previously fully rooted with supersu and the maskis one
Since this device tends to bootloop easily and because I've seen lots of questions about it and information is spread across many threads and posts, I'm writing this guide to help you guys troubleshoot bootloops before asking generic "help me" questions.
I) Terminology
1) BROM - A readonly memory on the SoC that runs right when the device boots. Loads the preloader. SPFT talks to it after authentication.
2) Preloader - MTK firmware that resides on flash. It is loaded on the chip's SRAM. It is responsible for initializing DRAM, and is one way of authenticating SPFT (the other is authenticating directly with the BROM, but I believe the way thi is done is known only to MTK and OEM engineers, and not even to authorized service centers). It also loads LK. Its source is distributed to OEMs, but is otherwise unavailable. Plenty of leaks for other devices can be found on the internet (some from the OEMs themselves).
3) LK - Little Kernel. This seems to be the most common platform for Android bootloaders. Mediatek has its own proprietary branch. Same source status as preloader. As an android bootloader, it is responsible for loading recovery or usual kernel image, as well as fastboot flashing.
4) Kernel - If you're on these forums, you should know what it is. You can find it in boot.img
5) DTBO - The device tree for the linux kernel. It specifies which hardware is available on the device. On usual (x86) PC platforms, the BIOS and Option ROMs store device information and offer it to the kernel (through UEFI/ACPI). As arm boards do not have such those, the linux kernel uses dtbos which play the same role.
II) Boot process
1) The ARM cores on the SoC start and jump to the address of the BROM.
2) (I'm not very sure of this, there's too little information) BROM puts the cores into a known state, should listen on the in-build UART for some time (half a decade ago, some leaks said something about 150ms), and if it doesn't receive anything, it loads the preloader.
3) The preloader initializes basic stuff like DRAM (phone's ram), watchdog, USB, etc. If the phone is connected to SPFT, it talks to it and authenticates it (the (in)famous "Account not authorized for this operation" should come from a check in here). I believe it also turns on the charging light. On a normal boot, it further loads lk. I belive that it also shows the chinese menu on pressing the Vol- button on factory preloader, but I did not check this.
4) LK (the one that comes with factory preloader) checks if Vol+ is pressed, and displays the bootloader menu (the one with the 4 english entries). When selecting recovery, it loads recovery. If normal boot is selected, it loads boot.img and dtbo.img and I believe it makes some checks on them (possibly of signatures, see the kernel trees). It then loads the proper image from the logo.bin partition and displays it (note: I've checked Logo Builder; rebuilding the logo.bin partition with it makes LK reboot before showing any image - this is done after the boot menu); examples are the one where it shows "Unlocked" or the Fastboot background. It also checks vbmeta for verified boot. Then it boots the selected entry.
5) The linux kernel does some hardware init, mounts system and starts Android's init.
6) Android does its usual init, mounting vendor, loading modules and firmware, turning on stuff like wifi, bluetooth, gnss, etc.
III) Tips for diagnosing bootloops
1) When bootlooping, plug your phone in a computer and check for the following (this is from my experience):
a) Charging light turning on
b) Vol+ menu showing up
c) Redmi logo showing up
d) Charging light turning off
e) Boot animation showing up
2) Things to do based on where things didn't work as in (1):
If (a) doesn't turn on, you're most likely in deep ****, and I'm not sure who can help you. Edit: Try pressing Vol+ and see if a device with VIDID 0x0e8d:0x0003 shows up. That would be the BROM. If it shows up, try using SPFT (most likely won't work, but you have nothing to lose anyway).
If (b), try SPFT. If it shows "Account not authorized", you have the stock preloader. There's a couple threads here with some methods that may or may not work. Otherwise, ATM you'll quite literally have to pay for your mistake. Grab your wallet and your Windows VM. You'll need them. Be prepared to search for the least shady guy that can help you and have your usb passthrough (on the upstream hub) ready.
If (c) - i.e. you have the menu but no logo, this means you've got LK. Since the Redmi logo doesn't show up, it means something is not quite how lk likes it (and lk is very picky on this phone). If you can, you'll probably want to use fastboot and flash a known good image for whatever you changed. If not, use SPFT.
If (d) - i.e. you have the logo but the charging light doesn't turn off, this means LK didn't boot the linux kernel. Flash a different (working) kernel.
If (e) - the charging light turns off, but you have no boot animation, this means either the kernel panics before it can start Android or that Android failed to boot properly.
From here on, you can use /sys/fs/pstore/console-ramoops to diagnose the problem.
If you do get a boot animation or are close to it, you might also want to try using adb logcat (especially if you've turned on adb debugging, and your ROM can do it on boot).
3) /sys/fs/pstore/console-ramoops
You can access it on a normal boot on some roms (or mount it manually if you've got root), or it's usually mounted automatically on TWRP. This is the kernel log from the last boot and is theoretically stored in RAM (I have reasons to doubt that). Basically, it works like dmesg, but for the last boot.
While it is polluted by zealous MTK debugging info, scrolling through it can often show where the problem is. If you can figure it out yourself, great. If not, post it here, and I (or somebody else) might try to figure out what went wrong and put it on a list of known bootloop reasons and fixes below.
4) Recommendations on posting about bootloop problems:
I think it would help a lot specifying which step from above fails. Also, if the charging light turns off, please, please provide /sys/fs/pstore/console-ramoops. You can easily get it with adb pull from TWRP and it helps *a lot* in figuring out what went wrong.
Hope this info will help you guys getting your devices working again faster (and provide more accurate info when asking for help).
P.S.: Another reference on MTK boot, also around 5 years old.
Reserved for List of bootloop problems:
Reserved
i have:
dm-verity error
Android system on your device is corrupted.
Device will boot in 5s
Click to expand...
Click to collapse
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
hello..
So... /sys/fs/pstore/dmesg-ramoops .. is not there .... /pstore do not exist :-\
and /proc/last_kmsg.. neither :-(
i have.. lineage-14.1-20190213-nightly-asanti-signed install it....
He will be generating them elsewhere???
OP, please add the infamous soft brick symptoms in detail, this maybe help someone in the future.
It shows redmi logo, it can enter vol + menu with some messages (I forgot the message), and it can enter vol - (bootloader), and it will ask for authorization when hooked to SPFT. And also link to that telegram post for work around.
And also, this is crucial info I found. Anything prior global 12.0.7 can be dirty flashed to anything prior that (even A10 to A9). 12.0.7 onward, 12.0.7 is the lowest you can get for dirty flash. I don't know for clean flash. Maybe work, maybe not.
fla5 said:
i have:
can't boot to my mobile in past week
just i can see my device with "fastboot devices" but not found with adb devices
and in device manager "Android ADB Interface" it's not recognize ( yellow question marks).
also have "adb server version (41) doesn't match this client (39); killing"
Click to expand...
Click to collapse
What have you done prior brick? Do you do something like flashing global rom in a locked bootloader chinese flavor phone? If yes, do the unbrick with SPFT. If not, and you have unlocked your bootloader and access to fastboot, I think dirty flash will do the trick.
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
luq90 said:
Sorry for being a lil' off-topic but I would love to ask how to prevent a bootloop after flashing back to stock recovery or/and boot. It happened twice - I used magisk+twrp, an update rolled out, I flashed the stock recovery for my official from (extracted from the official package) and ended up with a loop, did the mi authorized acc unbrick and it worked perfectly, now with the 12.5 rolling out I am preety sure i'll end with a loop again when I'll flash the stock boot or/and recovery.
Click to expand...
Click to collapse
you need to restore stock recovery and boot. and you can't install the update via updater nor twrp. install full rom via fastboot update or via mi flash (dirty flash is ok). but for 12.5 update, do it in twrp
from 12.0.7 onwards, downgrade without erasing data will lead to bootloop (just flash the correct build for remedy)
Thank you for your answer kekesed97.
Sorry, I made a small mistake. By saying that I used twrp means I had it installed not used for the flash. When the update came out, I thought that installing via ADB the stock recovery and boot will let me update the device like a completly unmodded model. Tried this Twice and always ended with a loop. Afterwards the only solution was updating via flashtools (it's bricked anyway so let's update manually hehe).
I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?
Is there a way to fix the crushed partition table without buying stuff?
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.