Database Users

I think I bricked my NS

I was flashing CM7. This is what I did:
Rooted, ClockworkMod v3.0.0.5 from Rom Manager.
From recovery did a BackUp (seems useless because it doesn't do anything.)
Wipe data/factory reset
Wipe Cache partition
Install zip from sdcard - selected cm7 - got a Status Error 7
Now the phone won't boot, stays on the Google screen, I can get into the recovery though.
Any ideas? I am downloading the Stock 2.3.3 image.
Thanks!

restore your backup.

irishrally said:
restore your backup.
Click to expand...
Click to collapse
I tried doing that from ClockworkMod, gave me an error, it was a ridiculously small file, doesn't seem like a backup.
Even the stock gives me a Status Error 7.
Any ideas?

you didnt brick, just download a a new rom, sounds like it was a bad download.. if the phone shows a screen it isnt bricked...

shabbypenguin said:
you didnt brick, just download a a new rom, sounds like it was a bad download.. if the phone shows a screen it isnt bricked...
Click to expand...
Click to collapse
{
"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 what I get. For both Stock 2.3.3 and CM7. I've tried multiple times.

right did you re download it and copy it back to the phone or just going off the rom you downloaded already? if so worst case shouldnt odin work?

shabbypenguin said:
right did you re download it and copy it back to the phone or just going off the rom you downloaded already? if so worst case shouldnt odin work?
Click to expand...
Click to collapse
I'm downloading it again. Should I rename it to update.zip? Odin, that's the software right?

I think your problem is because you are using the clockwork mod for I9020, where as for rogers you should be using clockwork for i9023 -- at least this was my case, I have i9020a rogers
you can get it from this link 2nd file.
after using this one you shouldn't be getting "E: can't mount cache" and you shall be able to repeat rooting/flashing steps.

crypticsorr0w said:
I think your problem is because you are using the clockwork mod for I9020, where as for rogers you should be using clockwork for i9023 -- at least this was my case, I have i9020a rogers
you can get it from this link 2nd file.
after using this one you shouldn't be getting "E: can't mount cache" and you shall be able to repeat rooting/flashing steps.
Click to expand...
Click to collapse
I was feeling so, either the ROM or the recovery. I'm just flashing the recovery, thanks for your help.
Also, how do I manually install ClockworkMod?

What is your computer OS? do you have android sdk?
In general everything you need is in this post
http://forum.xda-developers.com/showthread.php?t=955719

crypticsorr0w said:
What is your computer OS? do you have android sdk?
In general everything you need is in this post
http://forum.xda-developers.com/showthread.php?t=955719
Click to expand...
Click to collapse
It worked, I used fastoot and Terminal. Worked like a charm. Thanks again.

Bricked my MI A1 by updating a rooted phone

Hi folks,
My phone is unlocked & rooted and it only starts showing the android logo after I updated with the official updater in the phone, the december update.
When I want to flash it with the stock rom in fastboot mode, according to this (https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548 ), the flasher says just"can not found file flash_all_except_storage.bat"
I have no idea what to do.
Can anybody help me?
Don't want to throw away another 200 dollars
Thank you,
Michael

Youre missing a file in the stock rom

ProchyGaming said:
Youre missing a file in the stock rom
Click to expand...
Click to collapse
O rly?
I extracted the stock rom now with 7zip because it was a tgz and extracted the stock rom.
Now I used the flash_all.bat but it gets stuck at 'Writing system_a'.
Maybe because of lack of space.
ADB doesn't recognize my phone. Fastboot does. Can't go into recovery mode.
Partition table seems to be ****ed up. Any ideas? :/

OK, for all people with the same problem:
I used the linux scripts on my linux system and it booted / worked perfectly.
No idea why the windows crap didn't work.
Hope to have helped you

I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.

zeyaan said:
I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.
Click to expand...
Click to collapse
{
"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"
}

S7 Edge (Sprint) stuck in boot loop after attempting to root using Odin

Welp, I'm pretty sure I messed this up. Found a YouTube video (not even sure which one at this point, sorry) that was recently uploaded detailing how to root a Galaxy S7 Edge. Downloaded the firmware, opened up Odin, put it into Download mode, selected the Qualcomm firmware version for the AP field, and click start. It flashed correctly (according to Odin) and the phone began restarting and didn't stop. Just show's the "Galaxy S7 Edge" screen, goes black, and starts over.
I tried downloading the stock firmware for Sprint, load the appropriate files into Odin, and click start, I then get this output:
{
"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"
}
And on the phone, I see:
My build number is NRD90M.G935PVPS5BRA1, kernel version 3.18.31-12623509
I'm fairly certain this is entirely something that could have been avoided had I read more guides or instructions. Unfortunately, here I am! I really appreciate any help anyone can give me. I've been Googling and reading all morning, and I'm sure the answer is there, but I'll be damned if I can see it.

While I don't think there's much important info here, I figure it's at least showing some more in terms of version and name:

Your binary boot is v5. It won't work and you can't downgrade at the moment. What are you trying to do with root? There are many non root alternatives. To fix your bootloops, odin the stock firmware again.
Make sure you have the special version of odin too.
Also, download the stock firmware again. Try updato.com or plug the firmware version into android file host

lvpre said:
plug the firmware version into android file host
Click to expand...
Click to collapse
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.

reddeth said:
I don't know why I did not put together the relevance of firmware and the build number, but that was the issue all along it seems! After a dozen different cables, ports, and firmware versions I finally realized I needed to plug in the whole build number to find the firmware for that build specifically. Once flashed, the phone rebooted, asked to restore the backup based on the Google account, and it can text and make calls! Thank you so much for the help, I really appreciate it. I'll be sure to read and research a lot more before the next attempt to root a phone.
Click to expand...
Click to collapse
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.

lvpre said:
Glad it worked out...we all have been there at some point. Any reason you wanted to root? There may be some non-root alternatives available.
Click to expand...
Click to collapse
Mainly I was just wanting to get rid of the stock Sprint bloatware that you can't uninstall by default. If you've got any other suggestions for it, they're very much appreciated!

Boots only to TWRP - Need help fixing

Hi there. About a year or so ago I went about flashing my Tab but it went wrong and now all I can do is get it to boot to TWRP. Would someone be so kind as to tell me step by step what to do to get it back working? I'd prefer it to go back to stock ROM without TWRP or other 3rd party flash programs but I'll take what I can get. Help appreciated.
This is what I get when it boots:
{
"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"
}

Bump.

fuzzyreets said:
I'd prefer it to go back to stock ROM without TWRP
Click to expand...
Click to collapse
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?

DHGE said:
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
Click to expand...
Click to collapse
I got a reply! Thank you!
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.

fuzzyreets said:
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
Click to expand...
Click to collapse
What was the goal when you started down the path of installing TWRP? It seems like you might have been part way there if you got that far?
There are Lineage install instructions here. <-- More importantly Odin Download if you don't already have it.
If you decide to try Lineage, the latest builds require new firmware found here. It can also be obtained by returning to stock and updating.
Anyways If you are in TWRP, in the restart menu there is an option to restart to download. If will reboot to a black screen, just hit the power button once when the screen goes off. Before you do this, you need to obtain stock firmware, from somewhere. (Sammobile or something like that) You will also need Odin, link above.
As with anything proceed at your own risk.
Once you have those files, you can extract the firmware. They will be labeled and go into those spots in Odin, AP, BL, CSC, then you should be able to hit start. I'm going from memory, as I haven't had to restore mine since I got it (and looking at the files in stock firmware file).

Idk how relevant this is anymore but I had this same issue after I install lineage 18, there's a multi-disabler zip I got awhile ago that fixes all my flashing problems related recovery loop. Just Google that zip, flash it then format and restart. That what I've done easy fix, this assumes you followed the basic steps to properly flash whatever it is you're trying to.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"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"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin