need mmcblk0 for XT1925-3
or blank flash working
mmcblk0.img
Ambrosio71 said:
need mmcblk0 for XT1925-3
or blank flash working
Click to expand...
Click to collapse
Nobody?
Ambrosio71 said:
Nobody?
Click to expand...
Click to collapse
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
nate1975 said:
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
Click to expand...
Click to collapse
recover from a hard brick
Ambrosio71 said:
recover from a hard brick
Click to expand...
Click to collapse
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
nate1975 said:
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
Click to expand...
Click to collapse
in my case only the led flashes
there is still no blank flash file for XT1925-3
Ambrosio71 said:
in my case only the led flashes
there is still no blank flash file for XT1925-3
Click to expand...
Click to collapse
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
nate1975 said:
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
Click to expand...
Click to collapse
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Ambrosio71 said:
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Click to expand...
Click to collapse
Huh. Ok, so someone gave you an official beta, but won't supply you with the file you need to recover? Very strange. Hopefully someone else has that same device and can create a backup that you can use.
Related
When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?
irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up
I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823
Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.
I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.
Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.
Did you ever figure this out?
So,
In an attempt to install CWM, I've got to update to 10.26.1.18 for the version I want to go to.
I've attempted to use the manual process to no avail
Download the image
Put it on SD card at root after unzipping ONLY ONCE.
File name is UL-K00C-US-20.26.1.18-user.zip
Yes, it's a US SKU tablet, it's currently running JOP40D.US_epad-10.6.1.14.10-20130801
The card is formatted with FAT32, it's a 2g MicroSD card (I've tried a 32g SDHC Card as well)
I've cleared out the CMClient and the DMClient apps
I've even attempted to download it directly from ASUS support to the tablet itself, extracting locally, etc. no dice.
I've attempted to cold boot numerous times, wiped once, but I never get the notification in the lower right hand corner that there is an available update.
TL;DR TF701 can't find files for manual update, I'm about ready to throw it out the window.
kzersatz said:
So,
In an attempt to install CWM, I've got to update to 10.26.1.18 for the version I want to go to.
I've attempted to use the manual process to no avail
Download the image
Put it on SD card at root after unzipping ONLY ONCE.
File name is UL-K00C-US-20.26.1.18-user.zip
Yes, it's a US SKU tablet, it's currently running JOP40D.US_epad-10.6.1.14.10-20130801
The card is formatted with FAT32, it's a 2g MicroSD card (I've tried a 32g SDHC Card as well)
I've cleared out the CMClient and the DMClient apps
I've even attempted to download it directly from ASUS support to the tablet itself, extracting locally, etc. no dice.
I've attempted to cold boot numerous times, wiped once, but I never get the notification in the lower right hand corner that there is an available update.
TL;DR TF701 can't find files for manual update, I'm about ready to throw it out the window.
Click to expand...
Click to collapse
You put it at location /sdcard/
You dont put it on the microSD afaik
I thought also there is an update in settings before you do it? I dont remember exactly.
YayYouFixedIt said:
You put it at location /sdcard/
You dont put it on the microSD afaik
Click to expand...
Click to collapse
I have a copy of it there too...
No dice.
Also, to add to it, I have the device unlocked.
kzersatz said:
I have a copy of it there too...
No dice.
Also, to add to it, I have the device unlocked.
Click to expand...
Click to collapse
That doesnt sound good. Id wait to see what sbdags has to say. Not sure what you can do at that stage.
YayYouFixedIt said:
That doesnt sound good. Id wait to see what sbdags has to say. Not sure what you can do at that stage.
Click to expand...
Click to collapse
If I've gotta drop on an older version of CWM to flash a newer version of an OS to jocky it all around, i'm not adverse to the foot work, it's all just annoying lol
If you have 10.1.6.14.10 on it then you have flashed a TF700 boot loader on it.
Game over in my opinion. Not sure how you can recover from that.......
Unless you have a TF700? In which case you are in the wrong forum....... And flashing the wrong firmware.....
sbdags said:
If you have 10.1.6.14.10 on it then you have flashed a TF700 boot loader on it.
Game over in my opinion. Not sure how you can recover from that.......
Unless you have a TF700? In which case you are in the wrong forum....... And flashing the wrong firmware.....
Click to expand...
Click to collapse
Ha... you... wow.
I'm going to go hide now
Let me go test one thing and I'll report back
kzersatz said:
Ha... you... wow.
I'm going to go hide now
Let me go test one thing and I'll report back
Click to expand...
Click to collapse
Yeaaa, lock this.
Stupidity reigns supreme.
TF700; wrong guide, wrong recoveries, I'm very lucky I didn't brick it.
Thanks guys!
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.
i have read this post (https://forum.xda-developers.com/showthread.php?t=2581166) and this seems to be last hope to bring s3 mini back to life before touching JTAG.
Phone cant enter download mode, don't charge, don't show any sign of boot or bootloop.
If someone have debrick img for s3 mini gt-i8200, please give me link.
Or you can make by following instruction here:
(https://forum.xda-developers.com/showthread.php?t=2625628) and
(https://forum.xda-developers.com/att-galaxy-s6/help/create-debrick-img-stock-rom-t3367325)
Still waiting to get any help from XDA developers experts and users
Helloooo! I need the same, could somebody who knows how to do it just provide it for us? I'm willing to make a donation
marianvr7 said:
Helloooo! I need the same, could somebody who knows how to do it just provide it for us? I'm willing to make a donation
Click to expand...
Click to collapse
Not found yet. This unbrick image is needed when you messed up your bootloader, are you sure of that?
sadiqeen3210 said:
Not found yet. This unbrick image is needed when you messed up your bootloader, are you sure of that?
Click to expand...
Click to collapse
If you can't get boot into download mode at all, you might be done. Hard bricks are often the death call of a phone. I'm curious, were you able to work this out?
cloudmann said:
If you can't get boot into download mode at all, you might be done. Hard bricks are often the death call of a phone. I'm curious, were you able to work this out?
Click to expand...
Click to collapse
It can be worked out. See youtube for JTAG, and unbrick.img method. And there is also freezer method.
sadiqeen3210 said:
It can be worked out. See youtube for JTAG, and unbrick.img method. And there is also freezer method.
Click to expand...
Click to collapse
What's the Freezer method?
w0lf_b said:
What's the Freezer method?
Click to expand...
Click to collapse
see this thread, people are talking about freezer method here https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114/page53
It is a shame no one found the file. I have to buy a working device now I guess.
L3P3 said:
It is a shame no one found the file. I have to buy a working device now I guess.
Click to expand...
Click to collapse
Same model?
sadiqeen3210 said:
Same model?
Click to expand...
Click to collapse
Yes yes, an 8200n, I ordered one in bad condition but it boots so I will post the data here as soon as I got it!
I have copied the first 128M of the mmcblk0 of that device. Now I have no idea what to do. Maybe one of you have a better idea.
Hey, any progress here? I also need the img.
As I wrote, I got the raw data but I have no idea what to do with that!
Here is the raw dump of the beginning of internal flash. Flashing it directly to mmc (not to some partition but to /dev/mmcblk0 or similar directly) might recover booting. Then you have to wipe /system /data etc. and install an image from twrp, because OS is not included in this img. In case anyone has a better idea what to do with that, please tell!
https://l3p3.de/shr/goldenve3g-raw.img.gz
Thank you for your fast reply.
As I understand, the debrick img file is used to be written to a SD Card and the hard bricked phone should boot from that.
After flashing your image with Win32DiskImager or Etcher and putting it in the phone, it won't start.
When I flash the last file from this post (Debrick for 4.4.2) (Yes, wrong model). The SD-Card shows something like 26 partitions. That confirms this post:
should show approximately 23 partitions (IIRC)
Click to expand...
Click to collapse
Your img does not create any partition, but when extracted with binwalk, I can see that there are multiple files inside.
So I think your img is broken, how did you create it? Did you use this post or maybe this one? Can you replicate my partition list? Can you build it again?
I have just dumped the raw internal memory, the first x megabytes of it. It should contain partitions but I don't remember much.
I can look at it again later, have not much time now. But I have that phone and it will be done.
Hey, how are you? Do you have some spare time around?
Sorry, I worked a lot on https://github.com/L3P3/minicraft the last weeks. I have forgotten this thing. Next weekend, I try to do it.
It is an old phone, you should keep it but it does not hurry too much, right?
I also recommend buying a used S4 Mini [serranoltexx] and put Android 11 on it like I did.
Minicraft looks like an interesting project, I will keep an eye on that.
No, there is no hurry, I am trying it just for fun.