• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Idea for how to gain root on "new" Reverbs (unable to get root)

I think the new bootloader is not passing the panel_name to the kernel. We can try to modify the kernel as if the correct panel_name was passed without the bootloader. Or we can try to revert the bootloader. I think modifying the kernel is the safer solution. I hope someone can point me to the source code of recovery so that we can try this.
 
Got it. I will build a CWM recovery with modified kernel. I will post here after verifying that it works on my phone.
 
Interesting!
My bootloader version is androidboot.bootloader=M950VPALH6 and yours is a newer version M950VPBMD6. I am not sure why I didn't get the bootloader updated with the OTA but the older bootloader I have reports the LCD type as seen in my previous post. Yours does not report it. I am not sure if this causes any problem but this is all the difference I can see right now. Do you know if we can downgrade the bootloader?

I will check the OTA to see if there is a bootloader included.


I may have a backup copy of the MD6 ota update zip, I can check in the morning and upload it if you might find it useful.
 
I may have a backup copy of the MD6 ota update zip, I can check in the morning and upload it if you might find it useful.

I had saved the MD6 OTA when I had received it too. I checked the OTA file I saved and the new bootloader was not included in that. It would be good if you can double check. If you find the bootloader then it would be very useful to upload it.
 
This reminded me a past experience.

The new Reverbs that come with OOTB JB might have a different screen hardware. And the recoveries that we use with the earlier Reverbs don't have the proper drivers for the new screen. This could explain the screen problems. This had happened before with LG Optimus V. At some point after we already had the recoveries and kernels in place, VM started pushing new phones with different screens that came with a new ROM revision. Several/many users had soft bricks in their hands while trying to root.

We can reboot an OOTB JB phone and right after that pull a dmesg. Let's check which screen driver is activated and compare with an earlier phone with OOTB ICS. If somebody can post the dmesg with a newer phone, I can compare with the one I have.
I had the Optimus V, and even though the screen was different it showed only a black screen...and those were old optimus S screen, and Sprint doesn't have a Reverb.. so i think screen can be crossed off the list..I thought that at first...then remembered that
 
I have built a new CWMT-6.0.3.6 recovery with the MiRaGe kernel based on MD6 kernel source. I haven't changed anything in the kernel yet. The recovery works fine on my older version phone. If you can test this on a newer OOTB-JB phone, that would be great. I will modify the kernel next based on the feedback. Fingers crossed.

Tar file for flashing with Odin
cwmt-iconvmu-mirage_test1.tar
Zip file for flashing in recovery
cwm-touch-iconvmu-mirage.zip

I have used the zip file from Martinez as a base and the recovery configuration from Interloper. So, thanks to them.

Warning: The kernel and recovery are based on JB. Flashing on an ICS system is not recommended.
 
I have built a new CWMT-6.0.3.6 recovery with the MiRaGe kernel based on MD6 kernel source. I haven't changed anything in the kernel yet. The recovery works fine on my older version phone. If you can test this on a newer OOTB-JB phone, that would be great. I will modify the kernel next based on the feedback. Fingers crossed.

Tar file for flashing with Odin
cwmt-iconvmu-mirage_test1.tar
Zip file for flashing in recovery
cwm-touch-iconvmu-mirage.zip

I have used the zip file from Martinez as a base and the recovery configuration from Interloper. So, thanks to them.

Warning: The kernel and recovery are based on JB. Flashing on an ICS system is not recommended.

You are the MAN! We've got recovery!

I dunno what you did if you didn't touch the kernel yet, but it's definitely working.
 
I have built a new CWMT-6.0.3.6 recovery with the MiRaGe kernel based on MD6 kernel source. I haven't changed anything in the kernel yet. The recovery works fine on my older version phone. If you can test this on a newer OOTB-JB phone, that would be great. I will modify the kernel next based on the feedback. Fingers crossed.

Tar file for flashing with Odin
cwmt-iconvmu-mirage_test1.tar
Zip file for flashing in recovery
cwm-touch-iconvmu-mirage.zip

I have used the zip file from Martinez as a base and the recovery configuration from Interloper. So, thanks to them.

Warning: The kernel and recovery are based on JB. Flashing on an ICS system is not recommended.

mrg666 -

As discussed here are links to both the boot and recovery images for the OOTB JB. Hope I obtained them correctly and I hope they help with dev work.

recovery.img - https://docs.google.com/file/d/0Bx4PCBxYJmd1SnNBUEhzWmlJT2M/edit?usp=sharing

boot.img - https://docs.google.com/file/d/0Bx4PCBxYJmd1VXh1cDg2WThhVEU/edit?usp=sharing
 
You are the MAN! We've got recovery!

I dunno what you did if you didn't touch the kernel yet, but it's definitely working.

I changed the kernel in the recovery with MiRaGe. I just didn't do any specific change in my kernel yet. Recovery and kernel are both JB based now.

So, do you mean recovery works fine on the OOTB-JB Reverb now? That was it?
 
I changed the kernel in the recovery with MiRaGe. I just didn't do any specific change in my kernel yet. Recovery and kernel are both JB based now.

So, do you mean recovery works fine on the OOTB-JB Reverb now? That was it?

Looks like it. I've booted into recovery multiple times and successfully gotten root.

ydn680E.png
 
Looks like it. I've booted into recovery multiple times and successfully gotten root.

We are done here, then. Thanks for the confirmation. I have posted the recovery in its own thread so that everybody can find it.
 
Back
Top Bottom