follows the link of Stock Moto X4 ROM with Android 7.1.1 and September patch.
Model: X4 (Payton)
Version: NPW26.83-34-0-1
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The linked page shows a error, will be better if you can upload the file.
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
ebrandsberg said:
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
Click to expand...
Click to collapse
Just ran cat /proc/partitions.... dang, you are right
|payton_sprout:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 1048576 zram0
179 0 30535680 mmcblk0
179 1 3584 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 128 mmcblk0p9
179 10 128 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 256 mmcblk0p23
179 24 256 mmcblk0p24
179 25 112640 mmcblk0p25
179 26 112640 mmcblk0p26
179 27 1 mmcblk0p27
179 28 8 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 2048 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 6144 mmcblk0p36
259 5 6144 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 512 mmcblk0p39
259 8 128 mmcblk0p40
259 9 16384 mmcblk0p41
259 10 512 mmcblk0p42
259 11 8192 mmcblk0p43
259 12 65536 mmcblk0p44
259 13 65536 mmcblk0p45
259 14 16384 mmcblk0p46
259 15 16384 mmcblk0p47
259 16 1024 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 256 mmcblk0p50
259 19 256 mmcblk0p51
259 20 1 mmcblk0p52
259 21 1 mmcblk0p53
259 22 4608 mmcblk0p54
259 23 4608 mmcblk0p55
259 24 33424 mmcblk0p56
259 25 33424 mmcblk0p57
259 26 64 mmcblk0p58
259 27 64 mmcblk0p59
259 28 8192 mmcblk0p61
259 29 8192 mmcblk0p62
259 30 589824 mmcblk0p63
259 31 589824 mmcblk0p64
259 32 4227072 mmcblk0p65
259 33 4227072 mmcblk0p66
259 34 20262895 mmcblk0p67
179 32 4096 mmcblk0rpmb
252 0 4161104 dm-0
252 1 580580 dm-1
Click to expand...
Click to collapse
---------- Post added at 02:09 PM ---------- Previous post was at 01:56 PM ----------
Looks like the OP file was a leaked Brazilian version of the firmware... wonder if the boot.img is the same as US ?
And also looks like Motorola may be giving each variant of the device its own device name... not sure if this will be good down the line, development-wise, or not:
ro.product.name=payton_fi
ro.product.device=payton_sprout
Click to expand...
Click to collapse
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
saketkutta said:
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
Click to expand...
Click to collapse
Is this the partition scheme for Treble? If so, I'm fine with this personally, as it means they have thought ahead to help future-proof the phone (if there is such a thing).
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
crazyates said:
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
Click to expand...
Click to collapse
My custom OS on Nexus 5X took little more than 4 GB. Even if it was project treble (which is not confirmed yet BTW) it should not take more than 9 GB or 10 GB max. Mine out of the box it was 13 GB and something which is ridiculous)
Where did you get the ROM from? Link above is dead?
Iansip said:
Where did you get the ROM from? Link above is dead?
Click to expand...
Click to collapse
I don't think anyone got it here... I saw it bouncing around a couple Brazilian servers, but not open to download. Now that I look, it is the same Build # as the Project Fi version. So, hopefully it will turn up somewhere.
Seems the link in the OP is not dead, just goes to a secure server. It was originally posted on some G+ feeds, but no one has mirrored it yet, apparently
Actually, looks like that whole server is down right now. Every URL returns the same XML error. So maybe it will come back to life soon...
Oh, look at that... Moto has either geo or ISP restrictions on their download! VPN Proxy through server in Los Angeles, and download is running (sloooooowwwly).
Will update tomorrow morning.
UPDATE: Download died at 1.1 GB and the VPN workaround is no longer working. Grrrrr. Could probably extract boot.img anyway, but with no way to check the hash and no images to fall back on, too risky to actually patch/flash it
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
WARNING: This is unverified fimware for testing/research only. Please don't flash it and then complain when you paperweight your new X4.
UPDATED 10-27-2017: This ZIP has several corrupt files... verify anything against the MD5 in the "flashfile.xml" file before using!
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: 2702597112 bytes
SHA256 (unverified on the Motorola end!!!): 124f53fef572850532d029d00166829e200b777491502504c9de215fe7dd1046
DOWNLOAD: https://drive.google.com/open?id=0ByZWXbOZqmVqQ09FUXliN3hYMGs
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I'd love to see a unlock/root method. Hope to see TWRP asap!
Slickademo said:
How do you unlock and root? I just got mine today
Click to expand...
Click to collapse
Unlock is just a regular Motorola unlock... lot of threads on how that is done.
Root is a little more risky and complicated to explain here. The first thing we all need is a trusted factory image -- hopefully the one above is just that. I would suspect that once we confirm a factory image, root methods will be plentiful.
mightysween said:
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
Click to expand...
Click to collapse
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Oh, neat...definitely IP restricted then as I tried a VPN in LV and was still blocked. Wonder what the story is there!
Yes, if you end up with the same SHA256 let me know, we can at least be sure the file is intact.
---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Also FWIW, using that proxy link I posted gave me dl speeds of 2.5-3 Mbps, and plowed straight through to 100%.
mightysween said:
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: ~2.0 GB
CHECKSUM: UNVERIFIED! (my local SHA256: f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e)
DOWNLOAD: https://mega.nz/#!RkM2nSpL!4kHuZQfyHoSfeD-bfCcRxOi3A3rO7hz37RGcxRCglic
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
Also, if you wish to try a direct download from Motorola, this link may work... it is a proxy download through NordVPN. Again, no guarantees and no way to verify (though if you end up with the same SHA256 as above, there is good chance the file is intact).
DIRECT DOWNLOAD (via anon proxy): http://proxy-it.nordvpn.com/browse....cbNvGOLw5iqOebtX0lAb+hCJw==&b=1&f=norefer&pr=
Click to expand...
Click to collapse
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Code:
f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
gee one said:
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Click to expand...
Click to collapse
Thank you kindly! I downloaded again as well with same checksum, so I think we can assume the file is intact.
Related
Can someone please dump the partition mmcblk0p34 for me?
Command
dd if=/dev/block/mmcblk0p34 of=/sdcard/misc.img
Then upload it to dropbox or something.
Scaryghoul said:
Can someone please dump the partition mmcblk0p34 for me?
Command
dd if=/dev/block/mmcblk0p34 of=/sdcard/misc.img
Then upload it to dropbox or something.
Click to expand...
Click to collapse
Hey guys, someone lend this guy a hand if you can. He has done a lot of great kernel work on the EVO Shift! I'd help you Scary but I don't have a computer here for the next few days. Are you going to be deving for the 3D now?
I'm going to do it right now.
UPDATE: Error, Error Error.....user error I'm sure. I will see about getting this for you before work, but my computer is acting a fool.
lol i just did that for you and was about to post a link to my dropbox and i remembered im unlocked...doh....sorry
ty080279 said:
lol i just did that for you and was about to post a link to my dropbox and i remembered im unlocked...doh....sorry
Click to expand...
Click to collapse
What about S-OFF, is that okay or are you refering to just the HTC Unlock?
I only want an S-ON dump, so you may need temp root to grab what I want.
@Paul - Something like that, but we'll see how things go.
I'm guessing that's my error. I'm not getting full access having S-On, and my bootloader is still locked. I don't trust HTC. I'm not used to not being rooted. I'm not sure how to temp root 1.5, or if we can. I've never done temp root.
PM me. My 3D is still fully stock. If you wanna help a bit I will get it for you.
p34, that's the misc partition isnt it? Are you going to try to edit the mainver in the misc partition and try to downgrade the 1.50 Hboot? If so it doesnt work :-/ both myself and IEF from alpharev tried and it was a no go.. If you know another way, I could do you one better than just the misc partition, I can give you ssh access to my linux box and have a evo 3d hooked up to it that's s-on hboot 1.50 I just need a day or two to get my friend's from him and I can only have it for a day or two but can have it connected to the linux box non stop during that time
graffixnyc said:
p34, that's the misc partition isnt it? Are you going to try to edit the mainver in the misc partition and try to downgrade the 1.50 Hboot? If so it doesnt work :-/ both myself and IEF from alpharev tried and it was a no go.. If you know another way, I could do you one better than just the misc partition, I can give you ssh access to my linux box and have a evo 3d hooked up to it that's s-on hboot 1.50 I just need a day or two to get my friend's from him and I can only have it for a day or two but can have it connected to the linux box non stop during that time
Click to expand...
Click to collapse
Basically exactly what you said, we found that out yesterday for the evo shift as a downgrade option so we could root phones that had the ota. Joeykrim had already told me it wouldn't work on the 3d, but I was still curious what was on the misc partition, I opened up the shift & thunder bolt misc partitions for the older hboot already.
Shift thread, but you already know.
http://forum.xda-developers.com/showthread.php?t=1255474
Hmm, that would be nice but alas, I do not know a better way.
How much do you know about hboot? More specifically, the misc partition's FN0C strings, and the way htc & sprint sign packages, and how hboot verifies the signature.
I'm curious about the 3d's hboot before it's cracked because every single hboot version locked and unlocked has two similar strings. FN0C.
So I'm wondering if these are used in the verification or keys of some sort. For example, in RSA encryption there is public and private keys, public which encrypts and private which decrypts(I may have these backwards as it's been a very long time since I've done any encryption/decryption). So an example of practical use on sprint/htc's part would be encrypting with a key, then hboot decrypting it with FN0C. Although every encryption set of keys need to be related in some way since you can't just decrypt anything with any key. So it'd give a base to try and brute force finding the other key, or give us more information with how hboot works. Brute forcing an RSA key is generally unrealistic because of the sheer amount of time it'd take, but it'd be a fun learning experience messing with hboot.
edit: Well after a long afternoon I found out that sprint/htc takes a zip, takes it's sha256 hash and then encrypts that hash using an RSA private key, then stuffs it in the first 256bytes of the zip. Then when hboot loads it, it shaves off those 256 bytes and attempts to decrypt it using a public key.
Even disassembled hboot(Not using an arm disassembler though, couldn't find one, but an x86 one gave me an interesting output)
Doesn't look like misc has anything to do with the RSA encryption or hoot signatures though.
We did find it funny that out of 4 misc partitions on 3 different phones, FN0C showed up at the EXACT same offset, but it's probably nothing worth looking into.
So to anyone trying to decrypt this or recreate sprint/htc's signature algorithm, good luck.
misc partition
Scaryghoul said:
Can someone please dump the partition mmcblk0p34 for me?
Command
dd if=/dev/block/mmcblk0p34 of=/sdcard/misc.img
Then upload it to dropbox or something.
Click to expand...
Click to collapse
How do you know that's the misc partition ?
I have a HTC EVO 3D GSM version and I don't have that partition :
# ls /dev/block
loop0 loop7 mmcblk0p14 mmcblk0p20 mmcblk0p27 mmcblk0p5 platform
loop1 mmcblk0 mmcblk0p15 mmcblk0p21 mmcblk0p28 mmcblk0p6 vold
loop2 mmcblk0p1 mmcblk0p16 mmcblk0p22 mmcblk0p29 mmcblk0p7 zram0
loop3 mmcblk0p10 mmcblk0p17 mmcblk0p23 mmcblk0p3 mmcblk0p8
loop4 mmcblk0p11 mmcblk0p18 mmcblk0p24 mmcblk0p30 mmcblk0p9
loop5 mmcblk0p12 mmcblk0p19 mmcblk0p25 mmcblk0p31 mmcblk1
loop6 mmcblk0p13 mmcblk0p2 mmcblk0p26 mmcblk0p4 mmcblk1p1
justexpect said:
How do you know that's the misc partition ?
I have a HTC EVO 3D GSM version and I don't have that partition :
# ls /dev/block
loop0 loop7 mmcblk0p14 mmcblk0p20 mmcblk0p27 mmcblk0p5 platform
loop1 mmcblk0 mmcblk0p15 mmcblk0p21 mmcblk0p28 mmcblk0p6 vold
loop2 mmcblk0p1 mmcblk0p16 mmcblk0p22 mmcblk0p29 mmcblk0p7 zram0
loop3 mmcblk0p10 mmcblk0p17 mmcblk0p23 mmcblk0p3 mmcblk0p8
loop4 mmcblk0p11 mmcblk0p18 mmcblk0p24 mmcblk0p30 mmcblk0p9
loop5 mmcblk0p12 mmcblk0p19 mmcblk0p25 mmcblk0p31 mmcblk1
loop6 mmcblk0p13 mmcblk0p2 mmcblk0p26 mmcblk0p4 mmcblk1p1
Click to expand...
Click to collapse
The partitions between the cdma and GSM are different. And this thread is long gone...
Sent from my PG86100 using XDA
I know this thread is very old, But I didn't see the point of making a new one with one different word in the title.
Can someone with an Unlocked CDMA phone upload the misc partition to dropbox. I seem to have either a corrupted or incorrectly formatted partition.
I'm pretty sure its
Code:
/dev/block/mmcblk0p34
Or at least thats what all the errors point me to that.
Code:
E/STT:mtd ( 7738): mtd_open(): cannot find MTD partition [misc]!
D/STT:emmc( 7738): found emmc partition [misc]=[mmcblk0p34]
E/DMAgent ( 7738): the page size is -1, return false
E/DMAgent ( 7738): check_nand_info return abnormal!
E/STT:mtd ( 7768): mtd_open(): cannot find MTD partition [misc]!
D/STT:emmc( 7768): found emmc partition [misc]=[mmcblk0p34]
E/DMAgent ( 7768): the page size is -1, return false
E/DMAgent ( 7768): check_nand_info return abnormal!
Hello,
I think this is a hard one for you.
My unrooted Nexus 4 (Android 4.3) worked perfectly fine until the day I (randomly?) lost the signal (couldn't make phone calls or browse the internet ). I thought, hey that's not too bad, make a restart and it will work again.
Well instead of booting again it was stuck in a bootloop. So I reflashed stock 4.3, again bootloop, I tried to flash CM, bootloop, I cleared caches/wiped files constantly with twrp and CWM. Then finally I flashed stock 4.2, hey it booted!
But I had no IMEI number, nor a baseband version! So I flashed several baseband versions, neither worked (the bootloader-start screen showed the flashed versions though!).
So far I am searching for a solution all over the internet on how to restore the IMEI without a backup! Is there any hope for me? I have the IMEI number and tbh from my understanding this number has to be saved somewhere in hardware as well.
Any help appreciated!
- David
Btw. update from 4.2 to 4.3 -> Bootloop.
Just flashed 4.4 and it bootloops.
Ok, new idea, but I need your help for it.
What if I can restore my IMEI based on one of your "m9kefs1.img"? Can anyone provide me a working image of "m9kefs1.img", "m9kefs2.img" and "m9kefs3.img", this would be awesome!
hi...im having the same issue ...i tried almost everything without luck... i was thinking why google developers wont give us a solution for those who are outside the U.S. ...cause its real pain in the a** trying to send it to their service.
Same problem
dav1dde said:
Ok, new idea, but I need your help for it.
What if I can restore my IMEI based on one of your "m9kefs1.img"? Can anyone provide me a working image of "m9kefs1.img", "m9kefs2.img" and "m9kefs3.img", this would be awesome!
Click to expand...
Click to collapse
What you have in "/dev/block" ?
This is mine:
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 mmcblk0 mmcblk0p16 mmcblk0p23 mmcblk0p8 ram13 ram7
loop1 mmcblk0p1 mmcblk0p17 mmcblk0p24 mmcblk0p9 ram14 ram8
loop2 mmcblk0p10 mmcblk0p18 mmcblk0p25 platform ram15 ram9
loop3 mmcblk0p11 mmcblk0p19 mmcblk0p3 ram0 ram2 vold
loop4 mmcblk0p12 mmcblk0p2 mmcblk0p4 ram1 ram3
loop5 mmcblk0p13 mmcblk0p20 mmcblk0p5 ram10 ram4
loop6 mmcblk0p14 mmcblk0p21 mmcblk0p6 ram11 ram5
loop7 mmcblk0p15 mmcblk0p22 mmcblk0p7 ram12 ram6
News
I saved my "m9kefs1.img" & "m9kefs2.img"!
They are 2 files of 780KB with a lot of information, are they corrupted?
The problem are not the "files" in /dev/block but the contents of these 2 files:
Code:
m9kefs1 (/dev/block/mmcblk0p8)
m9kefs2 (/dev/block/mmcblk0p9)
I don't know if they are corrupted, because I can't compare them to mine, which are definitly broken.
News? On eBay I found an engineering sample with a "Repair EFS" program, where can I download it?
Thanks!
Help me! :banghead:
Android 4.4.1
Anyone have tried if Android 4.4.1 have bugfixed this problem?
PN.ItalyGirl said:
Anyone have tried if Android 4.4.1 have bugfixed this problem?
Click to expand...
Click to collapse
neither 4.4.1 or 4.4.2 factory images solve this unknow baseband / imei problem
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Rooting Coolpad Canvas (Cricket)
Me too having same issue as well, tried kingoroot
And king-root some got to like 30%... need help rooting it as well.. and maybe twrp would be great
But possibly could flash twrp using the coolpad's
Note 3 twrp for it, because they both have same
Resolution and screen size i believe, so for the porting shouldn't be all that hard.. any advice
Would be great..
Coolpad Canvas Root
joshglen said:
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Click to expand...
Click to collapse
SmartPhoneDeveloper said:
Me too having same issue as well, tried kingoroot
And king-root some got to like 30%... need help rooting it as well.. and maybe twrp would be great
But possibly could flash twrp using the coolpad's
Note 3 twrp for it, because they both have same
Resolution and screen size i believe, so for the porting shouldn't be all that hard.. any advice
Would be great..
Click to expand...
Click to collapse
I just ordered a coolpad canvas its coming on Saturday. I was able to root my last phone (Alcatel Onetouch Flint) which had no official guides on how to root it (so i made a guide). I might be able to do the same thing with this phone ill let u guys know if im able to root it when it comes.
Casey Campanile said:
I just ordered a coolpad canvas its coming on Saturday. I was able to root my last phone (Alcatel Onetouch Flint) which had no official guides on how to root it (so i made a guide). I might be able to do the same thing with this phone ill let u guys know if im able to root it when it comes.
Click to expand...
Click to collapse
Awesome!.. you won't believe how good this phone is for the price it has pretty powerful specs for the price and screen size is a whopping 5.5 inch and HD, I got mine for 49.99 when it was available at walmart luckily they had 2 left in Stock the day I went and got one.. but yeah I been trying to root it with no luck , but I'm not that good at programming when it comes to phones hopefully we can get this one rooted at least if anything .. it definitely deserves it being decently powerful phone here's the specs on it.. : https://ibb.co/ehJjtQ
Guys I was able to pull over 70% of the system files from it.. but for some reason it stops at when trying to pull WCNSS_qcom_cfg.ini file for some reason-(said permission was denied)??..hmm.., I will post pic shortly..
Any luck Casey on it?.. so far nothing working for rooting it yet you may have better luck than me..
SmartPhoneDeveloper said:
Any luck Casey on it?.. so far nothing working for rooting it yet you may have better luck than me..
Click to expand...
Click to collapse
No luck yet I tried kingroot, kingo app, towelroot, framaroot and some others nothing works. Still searching for a better method
So apparently it's harder to root nougat cuz of this new security feature. I feel like one click methods not gonna work
Well I also noticed when doing command get ver all that it said secured eMMc with the little kernel bootloader I'm sure there are ways around this but its going to require some help with someone that has higher phone developing skills than of my own of course.. also try command while connected to computer "adb pull system" without the quotes it got to 72% for me before it wouldn't write no more still have the files for system if anyone needs them for rewriting or porting in the bootloader ..
---------- Post added at 03:55 AM ---------- Previous post was at 03:43 AM ----------
Casey Campanile said:
No luck yet I tried kingroot, kingo app, towelroot, framaroot and some others nothing works. Still searching for a better method
Click to expand...
Click to collapse
Same here.. hmm , well if you or you can invite someone that maybe can port in or rewrite the little kernel bootloader to be unlocked, i have 72% of the system files.. still couldn't Figure out how to or where to extract the boot.img or recovery.img from?.. or the cache.img and the other .img files as well.. some of them or the .sh file in the system folder i extracted i believe may contain the answer?.. I'm sure for the rewriting of the bootloader but it's gonna require someone with better skills than of mine because i don't know how to rewrite little kernel bootloader image, but I'm sure for some this is a breeze though lol...
Oh almost forgot , from the building prop editor, i also managed to get the recovery key ID as well of someone knows how to port or rewrite the recovery.img, i know this will be of big help for sure this is the recovery key ID for the recovery image , i will post the pic of it shortly..
SmartPhoneDeveloper said:
Same here.. hmm , well if you or you can invite someone that maybe can port in or rewrite the little kernel bootloader to be unlocked, i have 72% of the system files.. still couldn't Figure out how to or where to extract the boot.img or recovery.img from?.. or the cache.img and the other .img files as well.. some of them or the .sh file in the system folder i extracted i believe may contain the answer?.. I'm sure for the rewriting of the bootloader but it's gonna require someone with better skills than of mine because i don't know how to rewrite little kernel bootloader image, but I'm sure for some this is a breeze though lol...
Click to expand...
Click to collapse
The mount points for where to pull the .img files from can't you find them by running cat /proc/mounts? These are the locations I got:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
SmartPhoneDeveloper said:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
Click to expand...
Click to collapse
Managed to get exact locations of each partition by running cat /proc/partitions and then running df to convert them into the common names. Here's what I got:
cp3636a:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 15267840 mmcblk0
179 1 102400 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 32 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 16 mmcblk0p17
179 18 4096 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 65536 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 3072 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 65536 mmcblk0p24
179 25 1024 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 65536 mmcblk0p31
259 0 32 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 384 mmcblk0p38
259 7 384 mmcblk0p39
259 8 384 mmcblk0p40
259 9 384 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 8 mmcblk0p46
259 15 65536 mmcblk0p47
259 16 2928640 mmcblk0p48
259 17 10876911 mmcblk0p49
179 32 4096 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 16384 mmcblk1p1
179 66 7744495 mmcblk1p2
253 0 2882924 dm-0
253 1 10876895 dm-1
253 2 7744495 dm-2
cp3636a:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 866276 5212 861064 1% /
tmpfs 947448 616 946832 1% /dev
tmpfs 947448 0 947448 0% /mnt
/dev/block/dm-2 7622740 879764 6726592 12% /mnt/expand/ad6a771b-2b4f-4d99-8f6d-640bb1ebd212
/dev/block/dm-0 2792600 2109896 666320 76% /system
/dev/block/bootdevice/by-name/cache 253920 368 248312 1% /cache
/dev/block/bootdevice/by-name/dsp 12016 5052 6640 44% /dsp
/dev/block/bootdevice/by-name/modem 102352 69776 32576 69% /firmware
/dev/block/dm-1 10574084 4527048 6030652 43% /data
/dev/fuse 7622740 879764 6726592 12% /storage/emulated
cp3636a:/ $
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
SmartPhoneDeveloper said:
Interesting... so with these mount points I'm assuming we should be able to do something I'm sure of it considering the zte zmax pro which also is qualcomm snapdragon processor and also utilizing same procedure of sorts and they managed to make twrp for it and also root so I'm sure same here ...which they some how put it into diagnostic mode or called **DFU mode and it allowed them to flash after mounting points was made with Linux OS
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
Also we you could possibly use also called QPST tool for Windows allows flashing of qualcomm processors as well ...
Click to expand...
Click to collapse
So using the location I tried to use the dd command to pull system.img but it said permission denied looks like it requires root:
dd if=/dev/block/dm-0 of=/storage/emulated/0/system.img
dd: /dev/block/dm-0: Permission denied
1|cp3636a:/ $
Don't know a whole lot about development but I'm pretty comfortable with using the Android back end and I'd be willing to help any way I can if there's something I can do or provide. This is such a neat little phone and I think it has a lot of potential.
Picked a canvas up on sale at bestbuy as a back up.. I must say its a nice phone for the money...
Now I just have to wait for coolpad- cricket to release unlock codes so I can use overseas travel.
Try this root
joshglen said:
I tried using kingo root, both on the phone and on the computer. I am not sure where to proceed from there. The main reason I want to root is to disable the startup sound, which does not get disabled automatically when I have my phone on mute. I tried using the sound disabler app from the play store, and it seems to not be working (the startup sound still plays).
Click to expand...
Click to collapse
Hi bro.. Try this root.. I tried in my coolpad canvas cricket but this root is only temporary because I have not found twrp to install super us..
https://forum.xda-developers.com/android/development/guide-to-root-coolpad-note-5-flashing-t3637644
Carzacamil said:
Hi bro.. Try this root.. I tried in my coolpad canvas cricket but this root is only temporary because I have not found twrp to install super us..
https://forum.xda-developers.com/android/development/guide-to-root-coolpad-note-5-flashing-t3637644
Click to expand...
Click to collapse
Here is a link to a TWRP build for the Redmi 4a, same exact internals as our phone. I mean the phones are exact all the way across the board. The best thing to do is to fastboot boot the .img first to see if it works 100%, and being on Nougat flash su systemless root. If it boots to TWRP from fastboot and you can flash su than we should be able to permanently flash TWRP from there. https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
zMILWAUKEE said:
Here is a link to a TWRP build for the Redmi 4a, same exact internals as our phone. I mean the phones are exact all the way across the board. The best thing to do is to fastboot boot the .img first to see if it works 100%, and being on Nougat flash su systemless root. If it boots to TWRP from fastboot and you can flash su than we should be able to permanently flash TWRP from there. https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
Click to expand...
Click to collapse
i tried it but my cellphone is bootloop .. when i do fastboot it says:
Now send the package you want to apply
to the device with "adb sideload <filename>". . .
Finding update package. . .
opening update package. . .
Verifing update package. . .
E:failed to verify whole-file signature
Update package verification took 0.7 s (result 1)
E:signature verification failed
Installation aborted.
Carzacamil said:
i tried it but my cellphone is bootloop .. when i do fastboot it says:
Now send the package you want to apply
to the device with "adb sideload <filename>". . .
Finding update package. . .
opening update package. . .
Verifing update package. . .
E:failed to verify whole-file signature
Update package verification took 0.7 s (result 1)
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
From what you're describing it sounds like you didn't do it correctly. In the bootloader it should never ask you to sideload anything. The correct steps are, with the phone on and adb debugging enabled, adb devices, should show your connected to your phone, next adb reboot bootloader, phone will restart into a download type screen, next step, on PC type fastboot devices to see if the PC and phone are communicating correctly, next is to type fastboot boot recovery.img, if it boots into the TWRP we're good, sorry but I don't have a PC up and running right now. So all I can do is suggest and hope you guys can get it running.
Anyone check into this and the comment that's on it, don't know if it will help, but just maybe.
https://mobile.twitter.com/srsroot/status/871056445315452933?lang=en
meatball702 said:
Anyone check into this and the comment that's on it, don't know if it will help, but just maybe.
https://mobile.twitter.com/srsroot/status/871056445315452933?lang=en
Click to expand...
Click to collapse
Don't do it, it's bull crap nothing but viruses. That srs spam link says they can root all phones, well if they could more devs on XDA would push it, but no it's a load of b.s.
I formatted a 64GB SD card via ADB into a ext4 partition for use as internal storage on Android and a FAT32 partition for use as portable storage. It worked well but after a while the ext4 partition became corrupt somehow, made a mess of my OS (Lineage) and I lost faith in the option of using an SD card as internal storage. I decided to format the SD card back to one FAT32 partition worth 64GB. But that proved impossible!
I tried with ADB, Diskpart and all kinds of other tools. I used the clean command in Diskpart but the partitions stay how they are and all data is still there on the FAT32 partition. The only change is that I can't copy anything into it. When I try, I see the data being copied there but when I leave the folder it was copied to and come back to it later, the files are gone!
Attached a screenshot from ADB and Diskpart. Perhaps that explains something?
Would appreciate any help and hint.
Cheers
BeyondReason said:
I formatted a 64GB SD card via ADB into a ext4 partition for use as internal storage on Android and a FAT32 partition for use as portable storage. It worked well but after a while the ext4 partition became corrupt somehow, made a mess of my OS (Lineage) and I lost faith in the option of using an SD card as internal storage. I decided to format the SD card back to one FAT32 partition worth 64GB. But that proved impossible!
I tried with ADB, Diskpart and all kinds of other tools. I used the clean command in Diskpart but the partitions stay how they are and all data is still there on the FAT32 partition. The only change is that I can't copy anything into it. When I try, I see the data being copied there but when I leave the folder it was copied to and come back to it later, the files are gone!
Attached a screenshot from ADB and Diskpart. Perhaps that explains something?
Would appreciate any help and hint.
Cheers
Click to expand...
Click to collapse
OK, so I can't attach or insert links due to newbie status. Here is the screenshot converted to text via OCR:
C: \adb \adb.exe
major minor #blocks name
179 8 15388672 mncblk8
179 1 15368 nncblk8p1
179 2 58816 nncblk8p2
179 3 512 nmcblk8p3
179 4 64 mncblk8p4
179 5 32 nmcblk8p5
179 6 2848 nncblk8p6
179 7 512 nncblk8p7
179 8 512 nncblk8p8
179 9 3872 nmcblk8p9
179 10 7136 mncblk8p18
179 11 18248 nmcblk8p11
179 12 14336 nncblk8p12
179 13 3872 nmcblk8p13
179 14 3872 mncblk8p14
179 15 13312 nmcblk8p15
179 16 15368 nncblk8p16
179 17 13312 nncblk8p17
179 18 7159 nncblk8p18
179 19 1 nmcblk8p19
179 20 8 mncblk8p28
179 21 8192 nmcblk8p21
179 22 9216 nncblk8p22
179 23 2568888 nmcblk8p23
179 24 284888 mncblk8p24
179 25 153688 nmcblk8p25
179 26 12288815 nncblk8p26
179 32 4896 nmcblk8rpmb
179 96 62367744 nncblk1
179 97 49893376 nncblk1p1
179 98 16384 nncblk1p2
179 99 12456943 nmcblk1p3
C:\windows\system32\diskpart.exe
Datenträger 1 ist jetzt der gewählte Datenträger.
DISKPART> clean
Der Datenträger wurde bereinigt. (the disc was cleaned)
DISKPART> list partition
Partition ### Typ (type) Größe (size) Offset
----------------- ---------------- --------------- ----------------
Partition 1 Primär 47 GB 1824 KB
Partition 0 Unbekannt 16 GB 47 GB
Partition 0 Unbekannt 11 GB 47 GB
DISKPART>
Rooted T-Mobile varriant.
Couldn't get Boombox to load.
Realized it is not supposed to work for my phone.
Went into TWRP.
Started a format on pretty much everything I could select.
4 hours later into my exfat format, I start thinking, yeah, this is... not... this is too long. I've destroyed it. SO, just to be sure it was a paperweight, I turned it off. Mid format... of every selectable partition in TWRP.
So anyway, it boots to fastboot now, and if I try to boot it into download mode, it starts TWRP but never loads. I put TWRP on my LAF partition as the root guide for H932 recommended it. The irony.
I CAN use ADB when I attempt to get the phone into download mode. Again, it does not actually have download mode, but instead a broken TWRP that never actually loads. The CLI TWRP found in sbin also will not actually start either.
If anyone could help me repartition this back to the point where I flash normal boot.img/system.img/recovery.img etc, well that would be, a godsend.
I will do, or answer any questions.
I do not know linux, but despite behavior that warrants wearing a helmet when I leaving the house, I promise I am competent enough to fix this, with some help.
Thanks people
--Edit--
cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
8 48 8192 sdd
8 49 2048 sdd1
8 50 4 sdd2
8 51 8 sdd3
8 64 286720 sde
8 65 40960 sde1
8 66 41472 sde2
8 67 41472 sde3
8 68 2048 sde4
8 69 2048 sde5
8 70 4096 sde6
8 71 4096 sde7
8 72 512 sde8
8 73 512 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 512 sde13
8 78 128 sde14
8 79 128 sde15
259 0 112640 sde16
259 1 512 sde17
259 3 512 sde18
259 4 512 sde19
259 6 512 sde20
259 7 512 sde21
259 9 512 sde22
259 11 512 sde23
259 12 512 sde24
259 14 512 sde25
259 15 512 sde26
259 17 1024 sde27
259 18 1024 sde28
259 20 4 sde29
259 22 1024 sde30
259 23 8192 sde31
259 25 128 sde32
259 26 128 sde33
259 27 8 sde34
8 96 8192 sdg
8 97 2048 sdg1
8 98 8 sdg2
8 80 8192 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 512 sdf3
8 84 8 sdf4
8 0 62103552 sda
8 1 49152 sda1
8 2 49152 sda2
8 3 32768 sda3
8 4 10240 sda4
8 5 6144 sda5
8 6 1024 sda6
8 7 32768 sda7
8 8 16384 sda8
8 9 8192 sda9
8 10 40960 sda10
8 11 67584 sda11
8 12 512 sda12
8 13 512 sda13
8 14 512 sda14
8 15 512 sda15
259 2 512 sda16
259 5 32768 sda17
259 8 8192 sda18
259 10 24576 sda19
259 13 2048 sda20
259 16 6465536 sda21
259 19 1253376 sda22
259 21 54000080 sda23
259 24 4 sda24
8 16 32768 sdb
8 17 3584 sdb1
8 18 4096 sdb2
8 19 2048 sdb3
8 20 1024 sdb4
8 21 1024 sdb5
8 22 8 sdb6
8 32 8192 sdc
8 33 3584 sdc1
8 34 8 sdc2
179 0 31166976 mmcblk0
179 1 31165952 mmcblk0p1
If ADB is indeed working, have you tried reflashing twrp to the LAF n' seeing if that does anything to get you back to a working recovery?
ls -al /dev/block/platform/soc/1da4000.ufshc/by-name
send output of this with adb shell
---------- Post added at 08:29 AM ---------- Previous post was at 08:24 AM ----------
4 hours later into my exfat format, I start thinking, yeah, this is... not... this is too long. I've destroyed it. SO, just to be sure it was a paperweight, I turned it off. Mid format... of every selectable partition in TWRP.
By exfat format, what do you mean?
the easiest would be to adb dd / push the laf partition back and work with it then, means: write laf, boot into dl mode, flash kdz. should work :good:
btw: which recovery version do you use? for determining which partitions were erased.
next time: formatting *only* needed for the main partitions, which are boot (not formattable) and system. don't touch any other partition mext time pls (at least in terms of formatting)
I don't have time to post the details, but right now you can fix your phone using dd. If you wipe out what you currently have thinking download mode will save you .. it might, but it might not and then you are stuck.
Gimme a bit to type up exactly what you need to do before you make it worse.
-- Brian
Renwark-Zipper said:
So anyway, it boots to fastboot now, and if I try to boot it into download mode, it starts TWRP but never loads. I put TWRP on my LAF partition as the root guide for H932 recommended it. The irony.
Click to expand...
Click to collapse
"I put TWRP on my LAF partition as the root guide for H932 recommended it. The irony."
Yeah, the only thing that literally saved you right now......
GI, you messed up your device, then blame the dev for a suggestion that will help you.....
Sent from my LG-H932 using XDA Labs
wow, so many partitions.
anyways, the "HIDE" button or use of HIDE tags is how you create spoilers and the pound sign or CODE tags is for code:
{
"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"
}
Ends up coming out like this:
hidden text here
or for code inside of hide:
Code:
hidden text here
BROKEN1981 said:
"I put TWRP on my LAF partition as the root guide for H932 recommended it. The irony."
Yeah, the only thing that literally saved you right now......
GI, you messed up your device, then blame the dev for a suggestion that will help you.....
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Reading titles is fun. It says "I'm the big dumb" right at the top. Notice the "I'm" that stand for "I AM". Translation: I'm not blaming the dev for anything, I AM THE ONE WHO DID THIS, THE ENTIRE POST OUTLINES MY STUPIDITY. The ironic part is I flashed over the download mode. Ya know, the one that lets you plug it into the computer and simply reflash with LGUP. If download mode was on the phone, this post wouldn't exist. End of story. I fully agree with his recommendation to have it on there, which is why I did it. The FACT, that it turned out to be the thing holding me back from fixing the phone was IRONIC.
sneak310 said:
wow, so many partitions.
anyways, the "HIDE" button or use of HIDE tags is how you create spoilers and the pound sign or CODE tags is for code:
Ends up coming out like this:
hidden text here
or for code inside of hide:
Code:
hidden text here
Click to expand...
Click to collapse
You're awesome, thanks!
I reported my own thread because I did not realize I cannot simply delete it myself. Do you know how to get this post deleted? I fixed the problem, but to be honest I can not remember all of the steps I took to do so. If someone finds themselves in a similar situation it might be nice to have this thread here, but as far as I am concerned I can be removed.
seadersn said:
the easiest would be to adb dd / push the laf partition back and work with it then, means: write laf, boot into dl mode, flash kdz. should work :good:
btw: which recovery version do you use? for determining which partitions were erased.
next time: formatting *only* needed for the main partitions, which are boot (not formattable) and system. don't touch any other partition mext time pls (at least in terms of formatting)
Click to expand...
Click to collapse
This is what I did! This works!
TWRP-3.2.3-7-DataIMG.img was the exact recovery used.
JohnFawkes said:
ls -al /dev/block/platform/soc/1da4000.ufshc/by-name
send output of this with adb shell
---------- Post added at 08:29 AM ---------- Previous post was at 08:24 AM ----------
4 hours later into my exfat format, I start thinking, yeah, this is... not... this is too long. I've destroyed it. SO, just to be sure it was a paperweight, I turned it off. Mid format... of every selectable partition in TWRP.
By exfat format, what do you mean?
Click to expand...
Click to collapse
I went into the wipe tab of TWRP and thought it would be a super idea to select everything I could, then change the file system to exFAT.
I'm... not sure what in the world I was hoping to actually accomplish with this. I had it in my head that If I formatted everything to one format, then back to the original, It might be a quick fix to my never booting custom rom.
It was not quick, and it was not thought through.
BrandonB1218 said:
If ADB is indeed working, have you tried reflashing twrp to the LAF n' seeing if that does anything to get you back to a working recovery?
Click to expand...
Click to collapse
I did try that, It did not work.
What seadersn outlined in his post is route I took to repair. Quite simple actually, I just did not really know what I was doing.
Renwark-Zipper said:
You're awesome, thanks!
I reported my own thread because I did not realize I cannot simply delete it myself. Do you know how to get this post deleted? I fixed the problem, but to be honest I can not remember all of the steps I took to do so. If someone finds themselves in a similar situation it might be nice to have this thread here, but as far as I am concerned I can be removed.
Click to expand...
Click to collapse
Nope, they don't let you delete threads here.
Renwark-Zipper said:
Reading titles is fun. It says "I'm the big dumb" right at the top. Notice the "I'm" that stand for "I AM". Translation: I'm not blaming the dev for anything, I AM THE ONE WHO DID THIS, THE ENTIRE POST OUTLINES MY STUPIDITY.
The ironic part is I flashed over the download mode. Ya know, the one that lets you plug it into the computer and simply reflash with LGUP. If download mode was on the phone, this post wouldn't exist. End of story. I fully agree with his recommendation to have it on there, which is why I did it. The FACT, that it turned out to be the thing holding me back from fixing the phone was IRONIC.
Click to expand...
Click to collapse
There is nothing wrong with pointing out differences of opinion over flashing duplicate/redundant TWRP to over the partition that has download mode and thus deletes download mode. I disagree with doing that, as do some developers in this forum. Not going to bother posting quotes, as I'm not starting an argument. Has been discussed in depth in the TWRP thread. However, other respected people recommend it, and they have their reasons. Looking the history of that suggestion, it really seems to be tied to T-mobile variants for reasons I don't wish to delve into here, but which I concede may be relevant to those T-mobile models.
Regardless, in my opinion it's not needed for most people and then when you DO suddenly need download mode, it's not there. The opposite point of view is "If you have TWRP, why would you ever need download mode?" I can think of a few instances... and their response would be, "Then (if/when you need it) re-flash the partition to get download mode!"
So, it's up to the users themselves to determine the priority of their needs and what likelihood will be for disaster recovery, one way or the other -- needing extra copy of TWRP vs needing download mode. There's no right or wrong answer.
Renwark-Zipper said:
The ironic part is I flashed over the download mode. Ya know, the one that lets you plug it into the computer and simply reflash with LGUP. If download mode was on the phone, this post wouldn't exist. End of story. .
Click to expand...
Click to collapse
Congratulations on not knowing what you are talking about. I think you can STFU now.
Sent from my LG-H932 using XDA Labs