trying to install http://forum.xda-developers.com/showthread.php?t=2181399 and it says my md5 is missing so there for i cant install the rom... cant figure it out and need to have my phone back.. also backup is failing as well
phatryan69 said:
trying to install http://forum.xda-developers.com/showthread.php?t=2181399 and it says my md5 is missing so there for i cant install the rom... cant figure it out and need to have my phone back.. also backup is failing as well
Click to expand...
Click to collapse
leave both those options unchecked when flashing. You check the MD5 on your PC using an md5 checking application or you can do it with an md5 check app on your phone, but not during flash.
exad said:
leave both those options unchecked when flashing. You check the MD5 on your PC using an md5 checking application or you can do it with an md5 check app on your phone, but not during flash.
Click to expand...
Click to collapse
but if my md5 is missing even b4 i flash what must i do then? cause i thought md5's were added in the file itself.
Read what Exad said and try again.
Turn off md5 checking in recovery and do it manually yourself before flashing.
Sent from my Evita
had no idea htc phones were such a PITA to install and such. long time samsung guy... i thought i did everything right but said failed when i tried to install...
Not really a pain in the ass, I've never had an issue.
So you turned off md5 checking and it still failed?
Did it give an error code?
Which recovery are you using?
Sent from my Evita
---------- Post added at 03:46 AM ---------- Previous post was at 03:22 AM ----------
PS. an md5 is not "added to a file", nor is it "a part of a file". An md5 is merely a hexadecimal readout of the contents of that file.
Here's how it works: A file is created, in our case it is a zip file. The creator or publisher of that file uses an md5 generator to generate the md5sum, which as I said before, is just a numerical readout (like a fingerprint) of the contents of that file. Now the end user has a tool to make sure that the file hasn't been compromised during a download or transfer. Using an md5 checker is a simple way to verify that the file is uncompromised. Input the md5 given by the publisher into an md5 checking app, then the app calculates the md5 of the file you've downloaded, if they match you know the file integrity is good.
Sent from my Evita
I don't find it to be a PITA either...
I mean, if you're rooting.. a lot of this stuff should be familiar or already make sense.
Idk just seems like I'm either missing a step or not doing something right.. I've followed everything I can as far as loading ROMs extracting boot.IMG and flashing in fast boot then booting into recov then flashing like u normally would and everything then pops up and says failed missing md5.. I can get root and everything fine but the minute I get to flashing a ROM I have a problem.. Maybe I needs step back and relook over what I'm doin
Using twrp btw
Sent from my SGH-I927 using xda app-developers app
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using?
Sent from my Evita
what ver. of twrp?
timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse
phatryan69 said:
timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse
I would recommend upgrading TWRP to 2.6.0.0. 2.5 had some issues with this phone (mostly with Sense ROMs in my experience). In TWRP > Settings make sure "Zip file signature verification" is unchecked. I think that sets the overall default. Otherwise I think you have to uncheck it each time on the screen where you "Swipe to Confirm Flash".
Click to expand...
Click to collapse
phatryan69 said:
timmaaa said:
So you've definitely disabled md5 check in recovery like suggested right? Which recovery are you using
i have everything unchecked that could be unchecked yes... and 2.5.0.0
Click to expand...
Click to collapse
2.5 has issues.
flash 2.6
then fastboot erase cache
then do a factory reset in twrp
Then try again.
Click to expand...
Click to collapse
having alot of problems with my computer nor recognizing my phone as well it seems... just uninstalled and reinstalled all drivers as well but only in bootloader when it says that trying to send commands to the phone.
installing 2.6
idk what i did but i got my phone on that rom and running...is there a list of fastboot commands somewhere?>
Not that I know of. Some that should work don't work also so... Maybe ill write one up later.
Sent from my HTC One X using xda app-developers app
phatryan69 said:
idk what i did but i got my phone on that rom and running...is there a list of fastboot commands somewhere?>
Click to expand...
Click to collapse
exad said:
Not that I know of. Some that should work don't work also so... Maybe ill write one up later.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just running "fastboot" will give you a list of sorts, but I don't know that most of those should ever be run by most of us. A list of the useful ones and what they do would be awesome, exad!
Code:
C:\Users\username>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
Since moving to cwm i haven't had an issue. I had tons of issues with twrp after 2.3.x.x i moved when cwm got official and haven't changed back. We also latest cwm builds from mdmower i believe the alias is, ill post a link when i get home.
DvineLord said:
Since moving to cwm i haven't had an issue. I had tons of issues with twrp after 2.3.x.x i moved when cwm got official and haven't changed back. We also latest cwm builds from mdmower i believe the alias is, ill post a link when i get home.
Click to expand...
Click to collapse
I've always had cwm might have to try that for a while
Sent from my HTC One X using xda app-developers app
Since TWRP 2.6 was released, I would have a hard time switching. They even made Wiping quicker and easier. I'd take a look at it if I was you. I've seen an issue with someone going from CM to TWRP and no longer being able to mount/access there SD card in TWRP. Dunno who's fault that is but they had to flash over an older non touch CWM and then fastboot erase cache and then flash TWRP. What a pain.
Related
Hi iv been testing this for a while and iv gotta say ..... its amazing the vega can do something the xoom cannot .... fastboot boot. Witch for a rom dev saves a lot of time
Ok this is relatively safe but is dev only thing so use with a little cation :-D as always dont blame me for a brick
[Video]
Watch it here
http://www.youtube.com/watch?v=llZ3qYSlLUE
[GUIDE]
From recovery
1) extract the .zip from below and allow the fastboot binary to be executes
2) reboot to recovery
3) format boot partition in recovery
4) reboot (now your device will drop to fastboot)
5) it will do this every boot until l boot.img is restored
From NVflash
1) extract the .zip from below and allow the fastboot binary to be executes
2) boot into APX mode
2) format boot partition with nvflash ( ./nvflash --bl bootloader.bin --format_partition 7 -go )
3) (now your device will drop to fastboot)
4) it will do this every boot until l boot.img is restored
[OTHER INFO]
Seeing as the vega reports as a different vendor we have to specify this in the fastboot command some examples can be found below
./fastboot -i 0x955 -b 0x10000000 boot zImage ramdisk
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 boot boot.img
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 flash boot.img
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 flash:raw zImage ramdisk
Click to expand...
Click to collapse
(This one is useful as u dont have to worry about a command line in normal cases)
[DOWNLOAD]
HERE !!!
Like to see a video of this is use...
Sent from my Vega using Tapatalk
Would love to give this a try but clearly I'm not a dev since I have no clue what to do
dagrim1 said:
Would love to give this a try but clearly I'm not a dev since I have no clue what to do
Click to expand...
Click to collapse
Ha ha, me to. I keep starting to think I am getting a handle on the scene and then something like this shows me how much I dont have a bloody clue!
Sent from my HTC Desire using XDA Premium App
gadgetuk99 said:
Like to see a video of this is use...
Sent from my Vega using Tapatalk
Click to expand...
Click to collapse
There is a video of this now in the main post
What is the advantage of this fastboot for a developer?
I remember getting that prompt when I switched from USB Slave to USB Host on Paul's Modaco ROM. I was quite clueless (I opened a help thread both here and in Modaco) and only re-flashing the stock ROM helped me any.
Nice work!
Does this allow you to push e.g. kernel images from my pc to boot on-the-fly or does the images need to be on the device already?
Sorry if that seems like a dumb question
FastBoot means that the device boots off a ROM image on your PC, instead of a burnt ROM. This has no advantage to non-devs (other then possibly brick protection, but they are pretty unbrickable as is).
To be clear: This does not make it boot "faster" and it probably has no use for you. Move along
Just checking. This'll be really useful in testing all of my broken kernel builds
how exacly does this work. Ive tried building roms in the past for my defy but got fed up with bricking it trying to bring the defy back to life was a real pain in the ass.
I would like to have a go with the vega if this makes it simpler.
Does it mean i can boot an image that is on my pc whilst leaving the internal image the same?
and can i simply re boot and have every thing as it was befor?
thanks in advange for any help!
I've extracted the advent .exe file to see if it'd be possible to re-flash the full stock ROM without having to use Windows. I got successful in reaching Fastboot mode, and when I execute ./fastboot I see a command which says "flashall", which would flash "boot.img", recovery and system.img. Would that be enough to boot safely? I see as well the possibility to execute an "update" command. If I converted the adventupdate.exe to adventupdate.zip, would said command flash the contents (aka the ROM?).
I may be saying foolish things, but I am curious about this.
Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !
Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.
..
Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!
..
Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.
Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.
..
Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !
hi
I have this file downloaded...
Code:
-rw-rw-r-- 1 root root 11956224 Nov 14 09:42 openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709 openrecovery-twrp-2.6.3.2-hammerhead.img
The md5 matches the one on goo.im...
Can I install this "safely" from a Android terminal emulator with the following commands...
Code:
#> su -
#> dd if=./openrecovery-twrp-2.6.3.2-hammerhead.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
and then would booting into recovery mode, would start TWRP ?
NOTE: THIS IS A QUESTION... ?
I wish goomanager has option of installing downloaded file... the site is giving 403 Forbidden...
ANYONE ???
Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app
yep i would flash using fastboot. permissions and stuff might get whacked if not done that way. Not sure just guessing.
Chromium_ said:
Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app
Click to expand...
Click to collapse
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryfile.img
Not difficult at all
Sent from my Nexus 5
TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
If you go to goo.im it shows that the file has been downloaded over 12071 times!!!
Code:
openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709
Size: 11.4 MB
MD5: 766b2361daf816eb168df37c55edb709
Link: http://www.goo.im/devs/OpenRecovery/hammerhead//openrecovery-twrp-2.6.3.2-hammerhead.img
Short Link:
(view file changelog)
2013-11-05 14:14:08 PST 12071
Yet every-time I try I get a 403-Forbidden...
My main issue is my Windows is dozing, and am on RedHat most of the time... My ubuntu desktop is in storage so I cant get to
any sort of fastboot...
anyways... I just managed to install the adt on my LMDE (LinuxMintDebianEdition) and am now playing with
udev files... and reading about how to get fastboot working..!
I felt dd was fairly native... and would not cause any permission problems...
anyways.. I will flash the image with fastboot, and then dump the recovery device with dd and check the md5sum..
if it matches, I will try to erase and load it again with dd and see if this method can work..
G
UPDATE
THE dd METHOD WILL NOT WORK
I got fastboot working, loaded the twrp image and rebooted to recovery and it works...
next I dumped the "/dev/block/platform/msm_sdcc.1/by-name/recovery" and checked its md5sum
and it does not match the twrp recovery... so I bet it will not work...
JUST USE fastboot...
MOD: We can close this thread... its answered (by myself)
Click to expand...
Click to collapse
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!
So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..
ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.
Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:
ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch
ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !
I need to warranty a phone but I need to turn it back to stock. I am using an older version of TWRP, I am guessing here but do I just download the factory image and flash it and I am done? It seems like everything I get when searching is geared towards the Pixel XL and using ADB rather than TWRP.
Thanks in advance.
Beacuse I part time as an internet troll, I have to chastise you for not reading threw this forum, because well that's why it's there, but hey we all can't use our Brian's all the time, but yes download the factory image for your phone Marlin for Pixel XL and Sailfish for Pixel unzip the file, make sure you have lastest usb drivers installed and click the flash all.bat.
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
jerryhou85 said:
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I'm not a good developer so I cannot answer you that question, but on Google official page, it is recommended to use fastboot or adb to flash factory images...
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
Because recovery and boot are sort of intermingled now. You would be writing over twrp at the same time you are trying to use it to flash.
Use the flashall bat file. If you want to save data edit out the -w from the bat file.
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I am on linux let me just get that out of the way.
So I used adb to fastboot the factory image but nothing happens
the file is in downloads and in the fastboot file. So I type cd Downloads, cd fastboot, fastboot sailfish-nmf260 it all looks good and you can tell adm is working but nothing happens on the phone.
I am current only able to get the phone into fastboot mode I dont know what I messed up but I can no longer even boot into TWRP.
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
twilk73 said:
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
Click to expand...
Click to collapse
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
robocuff said:
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
Click to expand...
Click to collapse
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
twilk73 said:
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
Click to expand...
Click to collapse
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Sgace said:
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
I don't think you can flash it with fastboot. In Windows, at the command prompt, you just type flash-all.bat and the batch file will run. It contains all the necessary fastboot commands. Perhaps that's where you're going wrong. Try just typing flash-all.sh. Leave the fastboot out.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
piperx said:
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
Click to expand...
Click to collapse
Sorry I wish I could try this. I had access to a windows computer at work and I was able to get everything done. After doing it at work I have a feeling I wasnt placing the files in the correct folder together to get it to start the update. It can be hard doing this on something other than windows for a dummy like me because most of the tutorials for things like this seem to be windows oriented. Regardless its done. I couldnt lock the boot loader on the windows computer though oddly but no big deal because I can do it on my laptop.
Thanks for all the help guys.